-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
(feature) Detect undefined variations with the linter #2562
Labels
Comments
kna
added
enhancement
New feature or request
needs-triage
A priority should be added to the issue
labels
Oct 23, 2024
@kna Yes this is very true, we should add this capability to the linter. Good catch 👌 |
thomaspoignant
added
good first issue
Good for newcomers
p1
High priority
ODHack9
and removed
needs-triage
A priority should be added to the issue
labels
Oct 23, 2024
/assign-me |
👋 Hey @thomaspoignant, thanks for your interest in this issue! 🎉 ⚠ Note that this issue will become unassigned if it isn't closed within 10 days. 🔧 A maintainer can also add the 📌 Pinned label to prevent it from being unassigned automatically. |
@thomaspoignant |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Requirements
A flag file might contain undefined variants due to a mistake.
I think it is better for the linter to report it as an error.
Example
The following flag file is incorrect because it uses an undefined variation(
NOT_IN_VARIATIONS
).But the linter does not report an error.
The text was updated successfully, but these errors were encountered: