* 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>
* created self-hosted section, moved installation guides, and re-edited first draft of the cloud quickstart guide
* refactored step 1 into two steps
* added media
* pre-mgmt submission proofread
* pulled down on wrong branch.
Revert "pre-mgmt submission proofread"
This reverts commit dfd678d083.
* first draft, halfway done
* first draft done
* added directus cloud section, first draft
* second draft, applied ben's desired edits
* moved resources out of intro and into separate page
* tiny tweaks
* heavily edited whats directus and tidied up lower sections
* link checked and proofedited with grammarly
* Update docs/getting-started/resources.md
* Update docs/getting-started/introduction.md
* Auto-format indentation
Co-authored-by: Rijk van Zanten <rijkvanzanten@me.com>
* Rename API Endpoints docs to Endpoints to align with Hooks
* Add a Creating Extensions page to the docs
* Update individual extension docs pages
* Apply latest changes to hook docs
* Move available events to a dedicated section in hook docs
* first half of broken links fixed
* next chunk of broken links resolved
* next chunk of urls
* last chunk of links
* one more
* filter rules
* homepage links
* removed localhost
* filter rules for query
* updated links
* relationships link
* changed links from references to glossary
* Make spinner success message bold in extension cli
* Expose extension-sdk cli functions
* Add create-directus-extension package
* Bump version
* Fix type fun times
Co-authored-by: rijkvanzanten <rijkvanzanten@me.com>
* Add support for _FILE environment variables
* Enhance processing of _FILE env vars
* Same processing as with other env vars (do not simply treat as string)
- tested successfully
* Warn if both variables are set (EXAMPLE and EXAMPLE_FILE)
* Add comments to make it easier to understand the code
* Set newKey only after file read was successful
* Don't convert value > MAX_SAFE_INTEGER to number
Thanks to @skizer!
As stated by @skizer (from #6119):
Altho it seems that we do have a numerical value
it can happen that its outside of Number.MAX_SAFE_INTEGER
thus resulting in a change of the original intended value
e.g oauth -> discord -> client_id
* Fix recursive logger-env import
Co-authored-by: rijkvanzanten <rijkvanzanten@me.com>
- Update fields translations use 'language' instead of 'locale'
- Replace all translation files from locale to language
- Update the docs with locale to language
