This repository has been archived by the owner on Aug 31, 2023. It is now read-only.
feat(rome_js_analyze): useCamelCase accepts function when they are used in new or exported #3210
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for rometools ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for rometools canceled.
|
xunilrj
force-pushed
the
feature/accept-camel-case-when-new-or-export
branch
from
4e0130d
to
2d31bb9
Compare
xunilrj
force-pushed
the
feature/accept-camel-case-when-new-or-export
branch
from
2d31bb9
to
72024f0
Compare
leops
approved these changes
Sep 14, 2022
1 task
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR add support for non camel case function when:
1 - They are used inside a new expression;
2 - They are exported.
Test Plan