-
Notifications
You must be signed in to change notification settings - Fork 680
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
Add config argument to specify valid markdown flavors #1424
Conversation
…/github.com/MilesMcBain/foam but make it general based on a new config in settings.json, "foam.supportedLanguages". That should allow for rmarkdown files as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! Thanks for contributing
Can you please fix the typo reporting? (see |
Sure! I used yarn to package the extension and was getting a warning about two lock files in a single project. I just renamed the npm one to disable it temporarily. Is it alright to remove the npm lock file entirely? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay it looks like removing that file takes care of the typo test.
Is there anything else needed? |
@allcontributors add @n8layman for code |
I've put up a pull request to add @n8layman! 🎉 |
all good, thanks @n8layman ! |
This PR attempts to address Problem 2 raised by @MilesMcBain in #1399 by implementing a configuration option, e.g.,
"foam.supportedLanguages": ["markdown", "quarto", "rmarkdown"],
, to specify valid markdown-like flavors as suggested in #924. This is my first PR to an open-source project, so please review carefully and let me know if there are any additional steps, tests, or changes needed!