You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jpmedley opened this issue
Oct 15, 2018
· 2 comments
Labels
docs ✍️Issues or pull requests regarding the documentation of this project.linter 🏡Issues or pull requests regarding the tests / linter of the JSON files.
Chrome runtime flags (accessed at chrome://flags have two forms: a string that appears as a heading and a URL anchor form. Google prefers that the anchor form be used because it's less likely to change than the string form.
This ticket is to track two tasks made at @Elchi3's request:
Document this preference in an appropriate place. (In the schema documentation?)
Make this testable so that existing and future references to flags will be corrected. (Schema change?)
The text was updated successfully, but these errors were encountered:
Elchi3
added
docs ✍️
Issues or pull requests regarding the documentation of this project.
linter 🏡
Issues or pull requests regarding the tests / linter of the JSON files.
labels
Oct 15, 2018
@Elchi3 Can you please hold off on updating the linter until you hear from me again. Many of our flags are not intended for tire kicking. We are working on pulling that information from Chrome Status. This request may turn out to be 'don't allow Chrome flags.' I'll keep you posted.
docs ✍️Issues or pull requests regarding the documentation of this project.linter 🏡Issues or pull requests regarding the tests / linter of the JSON files.
Chrome runtime flags (accessed at chrome://flags have two forms: a string that appears as a heading and a URL anchor form. Google prefers that the anchor form be used because it's less likely to change than the string form.
This ticket is to track two tasks made at @Elchi3's request:
The text was updated successfully, but these errors were encountered: