Skip to content
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

Future improvements dashboard 🗒️ #5

Open
4 tasks
fpapado opened this issue Oct 29, 2024 · 0 comments
Open
4 tasks

Future improvements dashboard 🗒️ #5

fpapado opened this issue Oct 29, 2024 · 0 comments

Comments

@fpapado
Copy link
Collaborator

fpapado commented Oct 29, 2024

This issue contains a list of current ideas for improvements to the libraries.

  • Surface more accurate parsing errors; use the line and column information to augment the information provided by the linters.
  • A browserbug/last-checked-updated rule, which tracks last-checked against new browser versions. The intent here is to tackle "currently active" bugs, and notify you when new versions of browsers show up in browserslist data.
  • A threshold or versionDrift or versionDriftThreshold configuration option, that offsets the threshold for erroring out vs warning. This might be different between ESLint and Stylelint. The intent is to allow ad-hoc customisations for last-checked bugs that are likely to take a while to fix. This option might not be useful for no-outdated.
  • A @browserbug feature feature-id or @browserbug-feature feature-id syntax, that consults Caniuse or BCD (browser-compat-data), in order to mark support targets. The aim here is to allow semi-automatic marking of workarounds, especially for feature-detection purposes.
@fpapado fpapado pinned this issue Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant