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.
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
Fixed a bug in EuiCodeBlock docs where import statement example was raised up and evaluated. #6595
Fixed a bug in EuiCodeBlock docs where import statement example was raised up and evaluated. #6595
Changes from 3 commits
da0d3f7
9de65d0
5646c97
30c7266
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
While this works, I'm not a fan because it's not actually targeting the issue we want to solve - which is to say, it's finding an
import
string within a code snippet that isn't actually an import. So if the import snippet in question changed toimport foo from 'bar'
, we'd still have the exact same issue.I would strongly rather fix this with a negative lookbehind to find any backtick character before any
import
statement and notReact
specifically. You should be able to accomplish this like so:Since regexes are incredibly hard to read, we should also document this new addition in the code above line 78:
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 pulled in your suggested change and ran it through Regex101 with a few test strings. It works well for our purposes here, as long as the template literal is the last item we're looking for.
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.
There should be no scenario where a real import comes after a template literal backtick - our current eslint rules ensure that all legitimate
import
s are at the top of the file, so this is a fairly safe assertion to make.