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

Passing string or number options to --use #26

Closed
cl8n opened this issue Jun 25, 2020 · 2 comments
Closed

Passing string or number options to --use #26

cl8n opened this issue Jun 25, 2020 · 2 comments
Labels
🙅 no/wontfix This is not (enough of) an issue for this project

Comments

@cl8n
Copy link
Contributor

cl8n commented Jun 25, 2020

right now, --use can take a format like this: toc=max-depth:3 with the part after equals sign being json options. however a lot of remark plugins take a string or number as an option rather than an object, and from what I can tell there's no way to pass those options in.

for example I'd like to do --use lint-list-item-indent=space, or --use lint-blockquote-indentation=2

@cl8n cl8n added 🙉 open/needs-info This needs some more info 🦋 type/enhancement This is great to have labels Jun 25, 2020
@wooorm
Copy link
Member

wooorm commented Jun 25, 2020

Hi there! That’s correct. Most plugins use objects. For legacy reasons, lint rules don’t. For a solution, can you use config files instead?

@cl8n
Copy link
Contributor Author

cl8n commented Jun 26, 2020

ah alright if it's just a legacy thing that seems fine. can use config files instead 👍

@cl8n cl8n closed this as completed Jun 26, 2020
@wooorm wooorm added 🙅 no/wontfix This is not (enough of) an issue for this project and removed 🙉 open/needs-info This needs some more info 🦋 type/enhancement This is great to have labels Jun 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🙅 no/wontfix This is not (enough of) an issue for this project
Development

No branches or pull requests

2 participants