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
Nuxt Content has Markdown Components notation.
I am very grateful to MDC VS Code extension for its help in implementing Nuxt Content.
However, there are many cases where it would be nice to be able to check statically like eslint-plugin-vue.
For example.
I want to detect a single : missing in an inline component before merging pull request
If the content creator is a non-engineer or does not use VS Code
etc.
Disucuss
We believe the segregation will be as follows.
eslint-plugin-vue → static check of /components/content/* eslint-plugin-nuxt-content (tentative) → static check of /content/*
However, we think it is necessary to consider the segregation from MarkdownLint.
(e.g., write No MarkdownLint in Docs like No Prettier in the Nuxt Contribution Guide).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Nuxt Content has Markdown Components notation.
I am very grateful to MDC VS Code extension for its help in implementing Nuxt Content.
However, there are many cases where it would be nice to be able to check statically like eslint-plugin-vue.
For example.
:
missing in an inline component before merging pull requestetc.
Disucuss
We believe the segregation will be as follows.
eslint-plugin-vue
→ static check of/components/content/*
eslint-plugin-nuxt-content (tentative)
→ static check of/content/*
However, we think it is necessary to consider the segregation from MarkdownLint.
(e.g., write No MarkdownLint in Docs like No Prettier in the Nuxt Contribution Guide).
Beta Was this translation helpful? Give feedback.
All reactions