The Wayback Machine - https://web.archive.org/web/20201225013309/https://github.com/reactjs/reactjs.org/issues/3120
Skip to content

/ reactjs.org

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

Jump to bottom

The prop value with an expression type of SequenceExpression could not be resolved. Please file issue to get this fixed immediately. #3120

Open
inblack67 opened this issue Jul 19, 2020 · 10 comments
Open

The prop value with an expression type of SequenceExpression could not be resolved. Please file issue to get this fixed immediately. #3120

inblack67 opened this issue Jul 19, 2020 · 10 comments
Labels
good first issue

Comments

@inblack67
Copy link

@inblack67 inblack67 commented Jul 19, 2020

I was just contributing to the docs a few minutes ago and after running

yarn check

got this warning

"The prop value with an expression type of SequenceExpression could not be resolved. Please file issue to get this fixed immediately." .

Thought I'd let you know.
@rickhanlonii
Copy link
Collaborator

@rickhanlonii rickhanlonii commented Jul 19, 2020

Do you mean yarn lint?

I get this as well, seems to be an eslint issue. Do you want to upgrade our eslint version to see if it fixes it?

Screen Shot 2020-07-19 at 3 13 39 PM
@inblack67
Copy link
Author

@inblack67 inblack67 commented Jul 20, 2020

I meant

yarn check-all

I tried upgrading eslint. No help!
@nawazkhan
Copy link

@nawazkhan nawazkhan commented Jul 20, 2020

jsx-eslint/jsx-ast-utils#95 could be the issue blocking.
@rrhg rrhg mentioned this issue Aug 27, 2020
Merged
@rrhg
Copy link

@rrhg rrhg commented Oct 8, 2020

jsx-eslint/jsx-ast-utils#101 was merged & should fix this.
@rickhanlonii
Copy link
Collaborator

@rickhanlonii rickhanlonii commented Oct 12, 2020

@rrhg do you want to submit the PR to upgrade?
@rrhg
Copy link

@rrhg rrhg commented Oct 14, 2020

I can try. If someone could provide some guidance that would be great. Thanks.
@rickhanlonii
Copy link
Collaborator

@rickhanlonii rickhanlonii commented Oct 15, 2020

@rrhg first step would be to figure out which dependency is using it and get that package to publish an upgraded version with the fix, then upgrade the version we use.
@rrhg
Copy link

@rrhg rrhg commented Oct 16, 2020

Did some research & if I understand correctly, the 2 dependencies using it are eslint-plugin-react & eslint-plugin-jsx-a11y.

eslint-plugin-react has a newer release tag (v7.21.4) that updated jsx-ast-utils to 3.0.0 & should fix this.

But for eslint-plugin-jsx-a11y, we have to wait for an active branch (v6.4.0) to be merged. Apparently it should be ready soon.
@rickhanlonii
Copy link
Collaborator

@rickhanlonii rickhanlonii commented Oct 16, 2020

Thanks for looking into it @rrhg!
@webrafaelso
Copy link

@webrafaelso webrafaelso commented Nov 4, 2020

Please update this thread if this already fixed. thanks
rrhg added a commit to rrhg/reactjs.org that referenced this issue Nov 4, 2020
@rrhg
Updated eslint-plugin-react to 7.21.5 & eslint-plugin-jsx-a11y to 6.4.1
64c1be3 
These updates fix issue reactjs#3120. The real problem was in jsx-ast-utils
which is a dependency of both eslint-plugin-react &
eslint-plugin-jsx-a11y
@rrhg rrhg mentioned this issue Nov 4, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue
5 participants
@nawazkhan @rickhanlonii @webrafaelso @rrhg @inblack67
You can’t perform that action at this time.