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
@W-17070457 Allow multi conditional !import.meta.env.SSR statements #171
@W-17070457 Allow multi conditional !import.meta.env.SSR statements #171
Changes from 18 commits
cda4062
894a09d
ed5fd4b
d8e13b6
a460184
8405da2
5bb6865
9458166
61da9ee
a6051fe
5bcd21c
51fbf1c
db05587
54c8123
8d09a50
9a45552
8dec5dc
a414851
2f4505d
d893920
759bd26
b071787
26b8e23
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.
If we want to be consistent about returning booleans (
!!
) then we'll also need to fixisMetaEnvCheck
since it can return undefined if it returnsnode.type
.Or we can just remove the
!!
because it's probably not important to return a boolean versus truthy/falsy. 🙂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.
This doesn't look correct at all. This test is only passing because it's using
this.template.querySelector
rather thanthis.querySelector
. We should open a separate issue to handlethis.template.querySelector
the same asthis.querySelector
.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.
this.querySelector*
detected, but notthis.template.querySelector*
#174There 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've updated the test to be this:
Seems to pass!
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.
Not sure an issue was opened but we have plans to migrate all
isCSR
into!import.meta.env.SSR
because they were not getting detected by the linter.