Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
fixed the schema of jsx-no-constructed-context-values.js#3766
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
@@ -41,7 +41,6 @@ ruleTester.run('react-no-constructed-context-values', rule, { | |||
}, | |||
{ | |||
code: 'function Component() { const foo = useMemo(() => { return {} }, []); return (<Context.Provider value={foo}></Context.Provider>)}', | |||
options: [{ allowArrowFunctions: true }], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
i understand that this is incorrect and should be removed.
however, must it be? I'm asking specifically if the schema change causes this to fail. if that's the case for end users, then the schema change is breaking.
380e32c
to51d342b
Compare
The schema for
jsx-no-constructed-context-values
did not seem to satisfy eslint'sRule.RuleMetaData["schema"]
type, so I fixed it.