-
-
Notifications
You must be signed in to change notification settings - Fork 681
Rule Proposal: vue/max-len #731
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
Comments
Hey @sebastianniemann Thanks for posting this issue. Implementation details of the core |
It's a good idea. We can add |
Please i need this! |
max-len
within the deepest flow content for any phrasing content or text node (template/html)
Good Idea! Also searched for that |
Can't wait for this to be implemented, it's definitely a must! I have |
Any progress ? |
Please describe what the rule should do:
Currently, any line within
<template>
is forced to respect themax-len
rule, without any option to ignore text-focused nodes (i.e. text nodes and phrasing content).This does not seems to be in line with the current ignore options for
max-len
, as it already allows to keep long string, URLs, template literals, RegExp literals, ... together in a single line.What category should the rule belong to?
It's a proposal to add an ignore option.
Provide 2-3 code examples that this rule should warn about:
The following examples should be fine (NO warning):
Text node within a flow content:
Phrasing node within a flow content
Additional context
This issue was already mentioned in another context (to deactivate eslint completely -- what should never be the recommended solution in my opinion) by @maxmilton (#260 (comment)):
The text was updated successfully, but these errors were encountered: