New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Iteration Release v5.5.0 #1178

Merged

akphi merged 1 commit into master from changeset-release/master

Jun 14, 2022

Contributor

github-actions bot commented May 23, 2022 •

edited

Loading

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```
#1166 41805dba (@akphi) - BREAKING CHANGE: Renamed LegendApplicationDocumentationRegistry to LegendApplicationDocumentationService; the corresponding exposed attribute from ApplicationStore is renamed from docRegistry to docService.

Minor Changes

#1166 41805dba (@akphi) - Add LegendApplicationAssistantService and VirtualAssistant which makes use of LegendApplicationDocumentationService to provide documentation library and contextual documentation for Legend applications.
#1191 353b505b (@MauricioUyaguari) - Add BasicValueSpecificationEditor to allow editing/updating basic value specifications like primitive values, time values (such as now(), today()), etc.
#1166 41805dba (@akphi) - Introduce LegendApplicationNavigationContextService, which is used to track user's navigation in the app using contexts (or area/layer of the app). This is crucial to support contextual documentation help provided by virtual assistant.
#1166 41805dba (@akphi) - Introduce LegendApplicationEventService which is used to manage application events, as of now, we only use it to notify events, i.e. as a direct replacement of EventNotifierService.
#1194 82fdd174 (@MauricioUyaguari) - Add LambdaParameterValuesEditor to edit parameter values for a lambda.

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

Minor Changes

#1166 41805dba (@akphi) - Add BasePopper component, popper is similar to popover, except that it does not come with a backdrop.

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```
#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use @jest/globals to import jest constructs, such as, expect, test, etc. We bumped into some problem when trying to disable injectGlobals in Jest config, so that would be left on as default for now, but at least with this change, we restrict usage of jest globals in the codebase.
#1190 4c076c98 (@akphi) - BREAKING CHANGE: Cleanup Webpack configuration utility: removed field extraBabelLoaderIncludePatterns.

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

Patch Changes

#1201 b700e876 (@YannanGao-gs) - Fix class's association property edges getting dropped when cleaning up the diagram. (#1200).

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```
#1105 436264af (@hardikmaheshwari) - Remove deprecated service-store protocols.

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```
#960 6ed0fcbc (@akphi) - BREAKING CHANGE: Renamed hashLambda to hashRawLambda

Minor Changes

#1166 41805dba (@akphi) - Expose getters for elements by type in graph, e.g. classes, enumerations, associations, etc.

Patch Changes

#960 6ed0fcbc (@akphi) - Adopt new grammar - JSON transformation API endpoints.
#1185 44544fc5 (@gayathrir11) - Fix populating of extendsClassMappingId for class mappings (#1181).
#870 8334cdcf (@abhishoya-gs) - Add GCP Workload Identity Federation Authentication Strategy

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```
#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use @jest/globals to import jest constructs, such as, expect, test, etc. We bumped into some problem when trying to disable injectGlobals in Jest config, so that would be left on as default for now, but at least with this change, we restrict usage of jest globals in the codebase.
#1166 41805dba (@akphi) - Removed EventNotifierService.

Patch Changes

#1189 997ef375 (@akphi) - Make sure network client overide Content-Type header properly when compression is enabled.

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```
#1166 41805dba (@akphi) - Remove AppHeader component.

Minor Changes

#1166 41805dba (@akphi) - Add virtual assistant to provide contextual help and documentation look-up.
#1194 82fdd174 (@MauricioUyaguari) - Support executing service queries with parameters.
#1166 41805dba (@akphi) - Remove application header, the menu bar is now moved to activity bar. Revamped About dialog (now called application info dialog) to show more informations around the extensions and allow user to copy application info to clipboard to make it easer for support.

Patch Changes

#1166 41805dba (@akphi) - Remove maximize/minimize feature as we are trying to simplify the status bar. This feature could easily be achived for wide-screen users by resizing browser window instead.
#1166 41805dba (@akphi) - BREAKING CHANGE: Update documentation key to dot-separated form.
#1183 8885ce46 (@YannanGao-gs) - Fix an issue with the rendering of SemiStructured columns in mapping source tree (#1182).
#870 8334cdcf (@abhishoya-gs) - Add GCP Workload Identity Federation Authentication Strategy
#1199 4ff8c329 (@akphi) - Properly reveal compilation error in text-mode when loading a project in viewer mode (#868).

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

Patch Changes

#1166 41805dba (@akphi) - Remove maximize/minimize feature as we are trying to simplify the status bar. This feature could easily be achived for wide-screen users by resizing browser window instead.

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

@finos/[email protected]

@finos/[email protected]

@finos/[email protected]

@finos/[email protected]

@finos/[email protected]

@finos/[email protected]

Major Changes

#1190 4c076c98 (@akphi) - BREAKING CHANGE: Use NodeNext (ESM module resolution strategy for Typescript). Read more about this here. This transition would be relatively smooth, except that we must use ESM-styled import (with extensions) for relative path. For example:
```
// before
import { someFunction } from './Utils';
// after
import { someFunction } from './Utils.js';
```

@finos/[email protected]

@finos/[email protected]

@finos/[email protected]

github-actions bot requested review from pierredebelen, akphi and MauricioUyaguari as code owners

May 23, 2022 19:52

finos-cla-bot bot added the cla-present label

github-actions bot force-pushed the changeset-release/master branch 6 times, most recently from 06c590b to 0860296 Compare

May 30, 2022 13:32

github-actions bot force-pushed the changeset-release/master branch 7 times, most recently from 6b641a3 to bf0642a Compare

June 7, 2022 04:48

github-actions bot force-pushed the changeset-release/master branch 7 times, most recently from 9bffc94 to 95dc266 Compare

June 9, 2022 17:22


          chore: bump versions and release

c0837ea

github-actions bot force-pushed the changeset-release/master branch from 95dc266 to c0837ea Compare

June 14, 2022 03:01

akphi merged commit 3538197 into master

akphi deleted the changeset-release/master branch

June 14, 2022 03:05

Contributor

akphi commented Jun 14, 2022

Note that, while migrating, the script below might be useful to update import statements

import { resolve, extname, dirname } from 'path';
import { existsSync, lstatSync, writeFileSync } from 'fs';
import { execSync } from 'child_process';
import { getFileContent } from '@finos/legend-dev-utils/DevUtils';
import { fileURLToPath } from 'url';

const __dirname = dirname(fileURLToPath(import.meta.url));

const pkgDir = resolve(__dirname, '../../packages/');

const files = execSync('git ls-files', {
  encoding: 'utf-8',
  cwd: pkgDir,
})
  .trim()
  .split('\n')
  .map((file) => resolve(pkgDir, file))
  .filter((file) => existsSync(file) && !lstatSync(file).isDirectory());

files.forEach((file) => {
  if (!['.tsx', '.ts', '.js', '.jsx'].includes(extname(file))) {
    return;
  }
  console.log('\nProcessing file: ', file);
  const content = getFileContent(file);
  const newContent = content.replace(
    /from\s'(?<imPath>.+)';/g,
    (importPath) => {
      const res = importPath.match(/from\s'(?<imPath>.+)';/);
      const imp = res.groups.imPath;
      if (imp.startsWith('.') && !extname(imp)) {
        const replacement = `from '${imp}.js';`;
        return replacement;
      }
      return importPath;
    },
  );
  writeFileSync(file, newContent);
});

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels