Skip to content
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.

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

refactor: Convert lib/plugins from CJS to ES module #427

Merged
merged 7 commits into from
Apr 10, 2020

Conversation

fayyazarshad
Copy link
Contributor

@fayyazarshad fayyazarshad commented Mar 13, 2020

Summary

This PR converts contents inside lib/plugins to ESModule.

Test plan

All unit test and Full stack compatibility suite tests pass.

@fayyazarshad fayyazarshad self-assigned this Mar 13, 2020
@coveralls
Copy link

Coverage Status

Coverage increased (+0.003%) to 97.225% when pulling 3785964 on fayyaz/convert-to-es6-plugins into 1e00509 on master.

@coveralls
Copy link

coveralls commented Mar 13, 2020

Coverage Status

Coverage increased (+0.003%) to 97.225% when pulling 7996a5a on fayyaz/convert-to-es6-plugins into 08deb5c on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.003%) to 97.225% when pulling 3785964 on fayyaz/convert-to-es6-plugins into 1e00509 on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage increased (+0.003%) to 97.225% when pulling 3785964 on fayyaz/convert-to-es6-plugins into 1e00509 on master.

@zashraf1985 zashraf1985 changed the title Converting plugin from CJS to ES module refactor: Convert lib/plugins from CJS to ES module Mar 16, 2020
@zashraf1985 zashraf1985 marked this pull request as ready for review March 16, 2020 22:10
@zashraf1985 zashraf1985 requested a review from a team as a code owner March 16, 2020 22:10
@zashraf1985 zashraf1985 removed the WIP label Mar 16, 2020
@fayyazarshad fayyazarshad force-pushed the fayyaz/convert-to-es6-plugins branch from b8c32ba to 7996a5a Compare March 24, 2020 07:01
Copy link
Contributor

@mjc1283 mjc1283 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have the same question as for #424: why introduce babel?

@fayyazarshad fayyazarshad force-pushed the fayyaz/convert-to-es6-plugins branch from 7996a5a to 848dfaa Compare April 8, 2020 11:20
@fayyazarshad fayyazarshad force-pushed the fayyaz/convert-to-es6-plugins branch from 3563b4f to eb549e0 Compare April 9, 2020 07:41
@fayyazarshad fayyazarshad removed the WIP label Apr 9, 2020
@fayyazarshad fayyazarshad reopened this Apr 9, 2020
@@ -55,6 +55,7 @@ describe('javascript-sdk', function() {
sinon.stub(configValidator, 'validate');

xhr = sinon.useFakeXMLHttpRequest();
global.XMLHttpRequest = xhr;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, wasn't this removed in an earlier PR? Why add it back?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was not causing any problem last time. but in this PR, when we made changes to the event dispatcher. Its somehow failing the tests. I still dont know the root cause but adding it back resolves the issue

@mjc1283 mjc1283 merged commit b141a94 into master Apr 10, 2020
@mjc1283 mjc1283 deleted the fayyaz/convert-to-es6-plugins branch April 10, 2020 00:06
jasonkarns added a commit to github/optimizely-javascript-sdk that referenced this pull request May 12, 2020
* v4:
  test suite doesn't pass cleanly
  prepare already runs build
  v4.0.0-github.0
  Ignore package tarballs
  Resume building non-minified ES entrypoint
  revert to master
  Expose an ESM-FULL bundle which includes optimizely deps
  Standardize ESM bundle
  Generate both min and non-min esm output
  exports option for es output is redundant. auto is best
  Use rollup --config- options for specifying bundles
  Build-all by default
  build various bundles using --config-* param
  chore: Prepare for 4.0.0 release (optimizely#468)
  fix: Removed React Native client engine temporarily (optimizely#466)
  chore: Prepare for 4.0.0-rc.2 release (optimizely#465)
  chore: Add source maps to build output (optimizely#464)
  fix(project config): Don't mutate the datafile object (optimizely#462)
  chore: Prepare for 4.0.0-rc.1 release (optimizely#461)
  chore: Prepare for js-sdk-datafile-manager 0.5.0 release (optimizely#460)
  chore(datafile manager): Remove react native datafile manager entry from package.json (optimizely#459)
  fix(datafile manager): Node datafile requests use gzip,deflate compression (optimizely#456)
  docs(datafile manager): Removed manual dependency installation requirement from docs (optimizely#457)
  chore(datafile manager): Added async storage as dev dependency (optimizely#455)
  refactor: Added a separate bundle for Json Schema Validator (optimizely#454)
  refactor: Convert lib/utils to ES module (Part 2/2) (optimizely#452)
  refactor: Convert lib/core to ES module (Part 2/2) (optimizely#450)
  chore(datafile manager): Update years in header comments (optimizely#453)
  refactor: Convert lib/core to ES module (Part 1/2) (optimizely#449)
  refactor: Convert lib/utils to ES module (Part 1/2) (optimizely#451)
  refactor: Convert lib/optimizely/* and lib/tests/* to ES module (optimizely#448)
  refactor: Convert lib/plugins from CJS to ES module (optimizely#427)
  chore: Update js-sdk-utils to 0.2.0 (optimizely#447)
  refactor: Convert entry points to es module and create minified bundles (optimizely#445)
  chore: Update CHANGELOG.MD for jsonSchemaValidator change (optimizely#443)
  Change functionality of JSON schema validation by removing skipJSONValidation entirely. Now a user needs to import jsonSchemaValidator from @optimizely/optimizely-sdk/lib/utils/json_schema_validator and pass it to createInstance when validation is desired. (optimizely#442)
  chore(datafile manager): Lint and formatting fixes for datafile manager tests (optimizely#441)
  [OASIS-6102]: changed functionality of the JSON schema validator module (optimizely#438)
  chore(datafile manager): Fix ESLint warnings & errors, apply Prettier formatting (optimizely#440)
  fix (datafile-manager): Fix boolean types, remove StaticDatafileManager, update READMe, add eslint + prettier (optimizely#436)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants