-
-
Notifications
You must be signed in to change notification settings - Fork 596
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
feat: Add support for custom EventEmitter #1999
Conversation
Thanks for opening this pull request! |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## alpha #1999 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 61 61
Lines 6141 6168 +27
Branches 1498 1499 +1
=========================================
+ Hits 6141 6168 +27
☔ View full report in Codecov by Sentry. |
@mtrezza This a new feature |
Do you mean this is a breaking change? |
Functionality is still the same but the new order allows the developer to control the flow. This shouldn’t be a breaking change. Moving |
I want to make sure I understand this correctly, you wrote:
Do you mean that currently (pre-PR) if a developer loaded LiveQuery before EventEmitter the SDK crashes, but with this PR that is not the case anymore? |
We don’t support ES6. The many JS frameworks that uses Parse rearrange the imports. Unless they use the minimized version, we have no control meaning developers don’t have control. |
Alright, if it's not a breaking change, we may just leave this open for a bit longer in case anyone from @parse-community/server has a comment on this. Otherwise we go ahead an merge. |
# [4.2.0-alpha.10](4.2.0-alpha.9...4.2.0-alpha.10) (2023-09-03) ### Features * Add support for custom EventEmitter ([#1999](#1999)) ([ca568a6](ca568a6))
🎉 This change has been released in version 4.2.0-alpha.10 |
# [4.3.0-beta.1](4.2.0...4.3.0-beta.1) (2023-09-16) ### Bug Fixes * `ParseUser.linkWith` doesn't remove anonymous auth data ([#2007](#2007)) ([7e2585c](7e2585c)) * Hard-coding of `react-native` path does not work for workspace builds ([#1930](#1930)) ([8222f3c](8222f3c)) ### Features * Add Bytes type to `Parse.Schema` ([#2001](#2001)) ([343d0d7](343d0d7)) * Add Cloud Code context accessibility to `ParseUser.logIn` ([#2010](#2010)) ([2446007](2446007)) * Add support for custom EventEmitter ([#1999](#1999)) ([ca568a6](ca568a6)) * Add support for excluding keys in `ParseQuery.findAll` ([#2000](#2000)) ([012ba4c](012ba4c)) * Add support to invoke a Cloud Function with a custom `installationId` via `Parse.Cloud.run` ([#1939](#1939)) ([eb70b93](eb70b93)) * Allow overriding `Parse.Error` message with custom message via new Core Manager option `PARSE_ERRORS` ([#2014](#2014)) ([be0c8a6](be0c8a6)) * Login with username, password and additional authentication data via `ParseUser.logInWithAdditionalAuth` ([#1955](#1955)) ([2bad411](2bad411))
🎉 This change has been released in version 4.3.0-beta.1 |
# [4.3.0-alpha.1](4.2.0...4.3.0-alpha.1) (2023-09-26) ### Bug Fixes * `ParseUser.linkWith` doesn't remove anonymous auth data ([#2007](#2007)) ([7e2585c](7e2585c)) * Hard-coding of `react-native` path does not work for workspace builds ([#1930](#1930)) ([8222f3c](8222f3c)) ### Features * Add Bytes type to `Parse.Schema` ([#2001](#2001)) ([343d0d7](343d0d7)) * Add Cloud Code context accessibility to `ParseUser.logIn` ([#2010](#2010)) ([2446007](2446007)) * Add support for custom EventEmitter ([#1999](#1999)) ([ca568a6](ca568a6)) * Add support for excluding keys in `ParseQuery.findAll` ([#2000](#2000)) ([012ba4c](012ba4c)) * Add support to invoke a Cloud Function with a custom `installationId` via `Parse.Cloud.run` ([#1939](#1939)) ([eb70b93](eb70b93)) * Allow overriding `Parse.Error` message with custom message via new Core Manager option `PARSE_ERRORS` ([#2014](#2014)) ([be0c8a6](be0c8a6)) * Login with username, password and additional authentication data via `ParseUser.logInWithAdditionalAuth` ([#1955](#1955)) ([2bad411](2bad411))
🎉 This change has been released in version 4.3.0-alpha.1 |
# [4.3.0](4.2.0...4.3.0) (2023-11-16) ### Bug Fixes * `ParseUser.linkWith` doesn't remove anonymous auth data ([#2007](#2007)) ([7e2585c](7e2585c)) * Hard-coding of `react-native` path does not work for workspace builds ([#1930](#1930)) ([8222f3c](8222f3c)) ### Features * Add Bytes type to `Parse.Schema` ([#2001](#2001)) ([343d0d7](343d0d7)) * Add Cloud Code context accessibility to `ParseUser.logIn` ([#2010](#2010)) ([2446007](2446007)) * Add support for custom EventEmitter ([#1999](#1999)) ([ca568a6](ca568a6)) * Add support for excluding keys in `ParseQuery.findAll` ([#2000](#2000)) ([012ba4c](012ba4c)) * Add support to invoke a Cloud Function with a custom `installationId` via `Parse.Cloud.run` ([#1939](#1939)) ([eb70b93](eb70b93)) * Allow overriding `Parse.Error` message with custom message via new Core Manager option `PARSE_ERRORS` ([#2014](#2014)) ([be0c8a6](be0c8a6)) * Login with username, password and additional authentication data via `ParseUser.logInWithAdditionalAuth` ([#1955](#1955)) ([2bad411](2bad411))
🎉 This change has been released in version 4.3.0 |
…)" This reverts commit ca568a6. # Conflicts: # src/Parse.ts
Pull Request
Issue
A lot of JS frameworks that uses Parse throws errors when trying to use event emitter.
Closes: #1412
Approach
Alternative
We could write our own EventEmitter in vanilla instead of
node:events
and polyfillingTasks