-
Notifications
You must be signed in to change notification settings - Fork 24
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
Warn against block.id usage #595
Open
miazbikowski
wants to merge
1
commit into
main
Choose a base branch
from
miaz/warn-block-id-usage
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+170
−2
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
miazbikowski
force-pushed
the
miaz/warn-block-id-usage
branch
2 times, most recently
from
November 15, 2024 19:38
c60ac80
to
14f7744
Compare
charlespwd
approved these changes
Nov 15, 2024
Comment on lines
27
to
52
return { | ||
// BAD: {% if block.id == "123" %} | ||
// BAD: {% if block.id == some_variable %} | ||
// BAD: {% if block[id] == "id" or block.id %} | ||
// FINE: <div data-block-id="{{ block.id }}"> | ||
// FINE:document.querySelector(`[data-block-id="${block.id}"]`) | ||
async Comparison(node, ancesors) { | ||
if (node.comparator === '==' && node.left.type === NodeTypes.VariableLookup && isUsingBlockId(node.left)) { | ||
reportWarning(context, node.position); | ||
} | ||
}, | ||
|
||
// BAD {% case block.id %} | ||
async VariableLookup(node, ancestors) { | ||
const parentNode = ancestors.at(-1); | ||
if (parentNode?.type === NodeTypes.LiquidTag && parentNode.name === 'case') { | ||
if (isUsingBlockId(node)) { | ||
reportWarning(context, node.position); | ||
} | ||
} | ||
} | ||
}; | ||
}, |
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.
So tidy. So simple. So beautiful 🥹
miazbikowski
force-pushed
the
miaz/warn-block-id-usage
branch
from
November 15, 2024 21:19
14f7744
to
651a723
Compare
miazbikowski
force-pushed
the
miaz/warn-block-id-usage
branch
from
November 15, 2024 21:23
651a723
to
c4813ff
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What are you adding in this PR?
Part of #463
We want to warn developers against the use of
block.id
in their liquid code in cases where the ID's instability could cause problems. This PR addresses usage inif
,elseif
,unless
andcase
blocks. (I've got some comments in the code to demonstrate the cases)Note: did not end up doing
assign
as a variable can have valid use cases (like those in my code comments)Follow ups
Dev docs PR
What did you learn?
console.log
will break your code and not tell you why. This is because of the language server.Before you deploy
changeset
allChecks
array insrc/checks/index.ts
yarn build
and committed the updated configuration filestheme-app-extension.yml
configchangeset
changeset