92621429ee
* add docs to eslint
* update prettier ignore
* fix vitepress linting
* eslint ignore fixes
* prettier run
* update prettier ignore
* fix formatting
* enable linting of markdown files
* revert format command change
* fix irregular whitespace
* update dictionary
* (Changelog) Create four-boxes-shake.md
* Rework ESLint / Prettier setup
- Disable js/ts/vue files for Prettier to ensure linting/formatting is
only happening via ESLint
- Rework formatting of code blocks in md files
- Disable formatting of code blocks in md files under '/docs' by Prettier
- Instead use "eslint-plugin-markdown" to format & __lint__ js*/ts*/vue such code blocks
- Replace unmaintained "eslint-plugin-md" plugin by official "eslint-plugin-markdown" plugin
- I'll check whether we can use this to format other code blocks
(json, html, ...) as well
- Restructure, clean-up and apply some fixes to the ESLint config
(Note: Not ready for flat config yet since not supported by
vscode-eslint)
- Enable cache for ESLint / Prettier in scripts
- Clean-up ignore file
- Explicit folder declaration (.../)
- Don't ignore all 'extensions' folders in ESLint (only
'/api/extensions/')
- Enable formatting in '/.github' folder
* Fix all formatting issues with Prettier
* Update md files under /docs/.typedocs
* Fix lint issues in vue/js files
* ESLint / Prettier config revision v2
Enable Prettier for md code blocks, but only as warnings since it can
get into the way with Vitepress md extensions like '[!code ...]'
comments
* Remove prettier-ignore comments
* Make spellchecker happy
* Remove changeset
* Revert lint setup for code blocks
There are many cases in the docs where linting / formatting of code
blocks doesn't make
sense:
- Code block is only an excerpt - linter fails
- Code block contains special comments (e.g. markdown extensions) which
needs to remain at the same place - formatting would break it
- ...
* Apply lint issues / formatting from temp lint setup
* Run formatter
* Fix merge failure
* Simplify & modernize ESLint / Prettier setup
No longer run Prettier via ESLint. Nowadays, this is the recommended
setup. There's no real need to run it this way, it's just an additional
layer.
Add VS Code settings to make the work with the new setup easier.
* Remove unused eslint disable directives
* Make editorconfig more useful
* Fix formatting issues reported by editorconfig
* Format files with Prettier
* Enable formatting of source translations file
* Format source translations file
* Remove unnecessary console error
* Remove unnecessary line
* Only ignore md files under .changeset
* Add CI reporter for Prettier
* Fail job on wrongly formatted files
* Fix format
* Test Prettier action on changed/added file
* Use simple CI format check for now & no cache
* Revert "Test Prettier action on changed/added file"
This reverts commit 4f7d8826ad.
* Introduce code blocks check for docs
* Fix code block issues
* Ignore auto-generated packages dir
* Fix comment position
* Also lint `/app/.storybook`
* Reformat modified files
---------
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
Co-authored-by: Rijk van Zanten <rijkvanzanten@me.com>
2.4 KiB
description
| description |
|---|
| You can support the project by becoming a Sponsor, by providing testimonials and reviews, and by sharing Directus with others. |
Sponsorship & Advocacy
Directus requires significant resources to build and maintain, especially as our community rapidly grows. If you'd like to help keep development active, please consider supporting Directus through sponsorship or advocacy.
Sponsorship
If you would like to help ensure Directus stays free, please consider providing financial support through GitHub Sponsors for as little as $1/month.
There's a range of perks available, including access to an exclusive Discord channel.
Sponsored Work
As a point of principle, we don't provide timelines for upcoming features or bug fixes. However, if you require specific work in a known time, Commissioned Features and Expedited Fixes are great ways to financially support the development of Directus and improve the codebase for the community and for your project!
Advocacy
GitHub Stars
As an open-source project, stars are a primary metric by which we measure our success. It only takes a few seconds to head to the Directus GitHub Repo and click the star. With enough activity in a short period of time, we get even more exposure on GitHub's trending page!
Social Posts
Engage with us on social media. Follow us! A quick post mentioning @directus goes a long way! Plus, we re-tweet the team's favorite shout-outs to our followers.
Testimonials
One sentence. Even that was a sentence and it was only two words! If you're a fan of Directus, we'd love to hear why with a short endorsement... More importantly, potential new users need to hear your testimonial to see if the product is right for them! You can leave a short written or video testimonial here.
Reviews
The following popular rating platforms allow you to post your rating and testimonial publicly, which automatically gives it more exposure.