Recently, set up a prettier config to normalize markdown formatting. It enforced no trailing semi colons which resulted in some mismatches if a dev has semis enabled extension wide. So firstly, this PR fixes that by removing that option.
Secondly, not all inline JS snippets were being fixed as such. Neither prettier, not eslint-markdown plugins natively handled that support (there still exists cases of js snippets without trailing semis). Also explored remark-lint but to no success. Concocted a custom linter (s/o claude) to handle all cases that occur in the repo and it should cover almost all use-cases (don't expect it to be perfect, have tried out manual examples generic in nature that do get filtered). Also, normalizes all ''```javascript' usages to '```js' for consistency
Recently, set up a prettier config to normalize markdown formatting. It enforced no trailing semi colons which resulted in some mismatches if a dev has semis enabled extension wide. So firstly, this PR fixes that by removing that option.
Secondly, not all inline JS snippets were being fixed as such. Neither
prettier
, noteslint-markdown
plugins natively handled that support (there still exists cases of js snippets without trailing semis). Also exploredremark-lint
but to no success. Concocted a custom linter (s/o claude) to handle all cases that occur in the repo and it should cover almost all use-cases (don't expect it to be perfect, have tried out manual examples generic in nature that do get filtered). Also, normalizes all ''```javascript' usages to '```js' for consistency