Skip to content

Latest commit

 

History

History
222 lines (138 loc) · 7.46 KB

CHANGELOG.md

File metadata and controls

222 lines (138 loc) · 7.46 KB

7.1.0

Updated dependencies

  • Fix version for ids-enterprise-ng to be at 18.2.4.

Known Issues

7.0.0

BREAKING CHANGES

There have been major version updates to angular and ids-enterprise-ng dependencies. These require NodeJS >= 18.13.0 (See Angular Version compatability) to be installed. Built-in support for Material Design has been removed.

Updated dependencies

  • Angular 18
  • IDS Enterprise Components 18

Upgrading from version 6

  1. Install a supported node version (>=18.13.0). Recommended to use nvm if you need to switch between different node versions.

  2. Install the latest CLI:

npm i -g @infor-up/m3-odin-cli@latest
  1. Remove current node_modules and package-lock.json from your project.
  2. Update all Angular 18 dependencies to "^18.2.4" in your package.json file.
  3. Update ids-enterprise-ng to "18.2.4"
  4. Run npm install

Upgrading - alternative

  1. With newest m3-odin-cli installed globally, create a new project.
  2. Open project and copy the dependencies and peerDependencies
  3. Add copied dependiencies to your project, remove duplicated old ones.
  4. Remove old node_modules and package-lock.json
  5. Run npm install

Known Issues

  • ids-enterprise-ng >18.2.4 is not working at the time of writing.

6.0.0

BREAKING CHANGES

There have been major version updates to many dependencies. These require NodeJS 16.x (LTS) to be installed.

Updated dependencies

  • Angular 14
  • IDS Enterprise Components 14

Upgrading from version 5

(Based on a newly created project with Odin version 5.0.0 odin new --soho --angular)

  1. Install the latest CLI:
npm i -g @infor-up/m3-odin-cli@latest
  1. Upgrade from Angular 12 to 13 (since ng update doesn't handle skipping versions):
# NOTE: I needed --force to deal with npm peerDependencies mistmatching in some packages
ng update @angular/core@13 @angular/cli@13 --force
  1. Stage/commit changes so that the working directory is clean (alternatively use --allow-dirty below)
  2. Upgrade from Angular 13 to 14, and other dependencies including Odin:
# NOTE: You might want to add karma, jasmine and other dev dependencies here as well.
# The update command won't do anything special when upgrading them, but you might need it to sync peer dependencies
ng update @angular/core @angular/cli ids-enterprise-ng @infor-up/m3-odin @infor-up/m3-odin-angular rxjs typescript

Known Issues

  • Issue with installing conflicting dependencies: infor-cloud#146
  • Some have reported an issue with running ng test after upgrading Karma. See this diff in karma.conf.js for how to replace the deprecated "karma-coverage-istanbul-reporter" plugin with the "karma-coverage" plugin.

5.0.0

Changes

  • cli: New IDS/Soho projects now uses the "new"/"uplift" theme by default, since this is the default theme in H5. Older applications are not affected by this.
  • samples: Added a Theme sample

Updated dependencies

  • Angular 12
  • IDS Enterprise Components 10.1

Upgrading from version 4

  1. Install the latest CLI
npm i -g @infor-up/m3-odin-cli@latest
  1. Upgrade existing project dependencies:
ng update @infor-up/m3-odin @infor-up/m3-odin-angular @angular/cli @angular/core ids-enterprise-ng

4.0.0

Changes

  • all: Updated dependencies
  • cli: The experimental-login command is now login. See here for more.
  • samples: Now using Highlight.js 10 in samples, fixed an issue where highlighting was not properly initialized.

Updated Dependencies

  • IDS Enterprise Components 9.1
  • Angular 11
  • Typescript 4
  • Highlight.js 10

Upgrading from version 3

  1. Install the latest CLI:
npm i -g @infor-up/m3-odin-cli@latest
  1. Upgrade existing project dependencies (assuming IDS & Angular is used):
ng update @infor-up/m3-odin @infor-up/m3-odin-angular @angular/cli @angular/core ids-enterprise-ng codelyzer

3.0.2

Bug fixes

3.0.1

This release contains major updates to dependencies (TypeScript, Angular, IDS Enterprise Components and more). It also contains a new (experimental) way of signing in to multi-tenant environments during development.

Upgrading

Existing projects can be updated with ng update. The process may differ depending on how the project is set up, and what other dependencies are installed. For a typical project using the IDS Angular Components, the following should do most of the work:

ng update @infor-up/m3-odin @infor-up/m3-odin-angular @angular/core@9 @angular/cli@9 ids-enterprise-ng codelyzer [email protected]

Don't forget to install the latest @infor-up/m3-odin-cli.

The IDS Angular Components may require changes to angular.json. See IDS Quickstart guide or this diff

Further update instructions are given by the ng update command and https://update.angular.io/

You may also need to install NodeJS 12.x (LTS).

Features

  • cli: New experimental-login command for multi-tenant login
  • angular: Possibility to configure IonApiService using the injectable IonApiConfig

Bug fixes

  • angular: IonApiService no longer uses XMLHttpRequest.withCredentials by default. This was causing CORS issues in some environments #41
  • cli: The development proxy will not forward CSRF requests and headers when proxying M3 requests to ION API.
  • cli: The development proxy will modify the Origin header so that POST requests are accepted by ION API.

Dependency updates

  • cli: Upgrade to Angular 9
  • cli: Requires NodeJS 12.x (LTS)
  • cli: No longer uses node-sass, which was not working on newer NodeJS versions.

BREAKING CHANGES

There have been major version updates to many dependencies. These require NodeJS 12.x (LTS) to be installed.

The IDS Angular Components require changes to angular.json to properly fetch assets, styles and scripts. New projects will not need to be changed, but older ones do. See Upgrading section above.

2.2.1

Bug fixes

  • core: Properly set CurrentCompany, CurrentDivision & CurrentLanguage on UserContext. Fixes #27 and #7

2.2.0

Features

  • core: Include CSRF token in requests to /m3api-rest. This will be required in future versions of M3.

If you for any reason want to opt out from this feature, you can do so by setting the IMIRequest.enableCsrf property to false:

const request: IMIRequest = {
  program: "...",
  transaction: "...",
  enableCsrf: false,
};

Older

For older releases, see https://github.com/infor-cloud/m3-h5-sdk/releases