* 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.
* proof-edited
* forgot to save before last comit
* fixed italic issue where I started with _ and ended with *
* tiny tweaks
* tiny tweak 2.0
* tiny tweak 4
* tiny tweak 5
* .gitignored package-lock.json that was created in the docs subfolder
* tweaked color names, except the ones in in vue files
* converted terminal screencaps into markdown
* updated images in 'Content'
* updated user-directory images
* updated media in file-library
* moved picsto cloud in reference>files
* updated images in config > datamodels > relationships
* updated primary colors in app-overview.svg
* updated insights images
* swapped quickstart-guide media and touched up copy
* Update last colors, remove linting from docs temporarily
* Fix theme color
* Update homepage header image
Co-authored-by: rijkvanzanten <rijkvanzanten@me.com>
* add images to content, file-library and user-directory pages of docs
* turn buttons from png to inline html and replace gifs with mp4s
* add a ton of icons everywhere
* add icons to presets & bookmarks
* add icons to webhooks
* add icons and clean up quickstart guide
* clean up icons and videos
* Move video assets to CDN
* Use updated video file naming system
Co-authored-by: rijkvanzanten <rijkvanzanten@me.com>
* 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
This slightly nicer syntax was introduced back in "npm@6.1.0".
"node@12.20.0", which is the minimum version we require, ships with "npm@6.14.8".
"npm@6" versions below "6.1.0" were never actually shipped with any node version, so it should be very safe to use this syntax.
