-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
ci: refactor lint CI task and fix lint issues #2004
ci: refactor lint CI task and fix lint issues #2004
Conversation
Thanks for opening this pull request!
|
I need a hand here with the CI step Lint (I should rename it in case it stays). It is failing to import |
# [4.0.0-alpha.16](parse-community/parse-dashboard@4.0.0-alpha.15...4.0.0-alpha.16) (2022-02-10) ### Bug Fixes * adding internal class (e.g. `_User`) fails due to prefixed underscore ([parse-community#2036](parse-community#2036)) ([f80bd07](parse-community@f80bd07))
# [4.0.0-alpha.17](parse-community/parse-dashboard@4.0.0-alpha.16...4.0.0-alpha.17) (2022-02-23) ### Bug Fixes * security upgrade prismjs from 1.26.0 to 1.27.0 ([parse-community#2047](parse-community#2047)) ([3afb24e](parse-community@3afb24e))
Snyk has created this PR to upgrade @babel/runtime from 7.17.0 to 7.17.2. See this package in npm: https://www.npmjs.com/package/@babel/runtime See this project in Snyk: https://app.snyk.io/org/acinader/project/3e039b91-2450-4b56-8420-baf56cab388e?utm_source=github&utm_medium=referral&page=upgrade-pr
@mtrezza It looks like the parse SDK cannot be loaded by Jest in Node v16, causing several tests to fail. However, this doesn't seem related to the SDK package itself (all tests passing OK in v16) So far, the only workaround I found is to use the flag Let me know your thoughts. If you find it ok, we're ready to merge. |
It's likely that we have some unhandled rejections, I remember we have (had?) this issue in Parse Server as well. |
The only issue I see with adding the flag is that it may obscure issues with unhandled rejections. Especially since we are running tests, I am not sure whether it makes sense to run them in a non-representative environment. We may see tests pass, but dashboard won't actually run in certain Node environments. How about the Parse JS SDK, in which Node versions do its CI tests run? |
I think you’re right. The SDK CI is running on v14. Should we drop support for v16 until the SDK officially supports it? |
I think that would be the process. Do you want to open a PR in the JS SDK and add Node 16 to the CI? Once it runs on Node 16, we could continue here without any errors hopefully. |
Finally fixed. No need to modify the SDK repo. It was enough to mock the module |
I hope I resolved the conflicts correctly in package-lock. Let's see whether it passes. |
@RaschidJFR Could you take a last look before merge, since this has been stale for some days. Note to myself:
|
LGTM. Thanks @mtrezza |
🎉 This change has been released in version 4.1.0-alpha.2 |
New Pull Request Checklist
Issue Description
Currently, the commands
npm test
andnpm run lint
are failing: some files are not following style rules and there are some outdated test cases.Approach
TODOs before merging
Add changes to documentation (guides, repository pages, in-code descriptions)