* Add extra error handling for invalid messages
* added description and logging
* renamed fix function
---------
Co-authored-by: Rijk van Zanten <rijkvanzanten@me.com>
* fix#7420 ignore extra envs for mysql
* Update contributors.yml
* Run formatter
* Add changeset
---------
Co-authored-by: rijkvanzanten <rijkvanzanten@me.com>
* add isolated-vm@4.6.0
* add mvp replacing vm2 with isolated-vm, two env vars
* make copying async and add tests
* add env vars to docs
* remove isolate-logging function
* update docs for FLOWS_EXEC_ALLOWED_MODULES removal
* further removal of allowed module usage
* rename env vars and their usage, remove script "compiling" and replace Reference with ExternalCopy
* remove logging and catching, let the outer executeOperation function do it
* remove vm2 from dependencies
* remove unused var
* run prettier formatting
* run eslint
* create changeset
* rename env var without unit suffix, add minimum to doc
* add two tests for config testing
* fix 'mb' spelling
* update changeset
* Mark it as major change for `@directus/api`
* Breaking change copy
* add logging from the operation
* run linting
* Update docs/releases/breaking-changes.md
* Update docs/releases/breaking-changes.md
* run linting, make operation cursive
* Mention HTTP requests in breaking changes
* make linter happy
* changed cursive to bold (asked kevin)
* add to the test for timeouts
* run linter
* Update api/src/operations/exec/index.ts
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
* Update api/src/operations/exec/index.ts
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
* Update note on run script modules
* Update breaking changes
* Update docs/app/flows/operations.md
Co-authored-by: ian <licitdev@gmail.com>
---------
Co-authored-by: Rijk van Zanten <rijkvanzanten@me.com>
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
Co-authored-by: Kevin Lewis <kvn@lws.io>
Co-authored-by: ian <licitdev@gmail.com>
* Redact env values in revisions for Flows
* Add unit tests
* Create cold-maps-teach.md
* Redact string type envs only
Co-authored-by: Brainslug <br41nslug@users.noreply.github.com>
* Fix linting
* Update test for non-string env
* Ignore zero length strings
Co-authored-by: Brainslug <br41nslug@users.noreply.github.com>
* Add replacementFn to include key of redacted value
* Update cold-maps-teach.md
* Remove case insensitivity
* Update changeset
* Rework
* Add utils to changeset
* Add unit test
* Rename to getRedactedString and add REDACTED_TEXT
* Consistent naming
---------
Co-authored-by: Brainslug <br41nslug@users.noreply.github.com>
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
* Fix using wrong type for default values
* fix for readAll
* Format file
* Add changeset
---------
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
* Initial commit to add supabase as a storage driver
* Working supabase implementation
* Slight cleanup
* Started working on tests for storage-driver-supabase
* Updates
* Initial commit to add supabase as a storage driver
* Working supabase implementation
* Slight cleanup
* Started working on tests for storage-driver-supabase
* Updates
* Nicer working tests
* More working tests
* Readable stream
* Working version with all passing tests and types
* Update contributors.yml
* added documentation
* Ran prettier to fix formatting issues
* Ran linter and added Supabase to dictionary
* Fix tsconfig reference
* Organize imports
* Start at v0
* Add changeset
* Lock versions
* storage-driver-supabse: Added fullpath for move and copy arguments
* storage-driver-supabase: Removed resumable uploads
* Update lockfile
---------
Co-authored-by: Rijk van Zanten <rijkvanzanten@me.com>
* Remove res.status calculation as it is set later
* Ensure 500 is thrown on multiple errors of different types
* Add changeset
---------
Co-authored-by: rijkvanzanten <rijkvanzanten@me.com>
* Using the same data fetching logic for rest and graphql
* Create fresh-snails-knock.md
* checked and tested data fetching code
* always fetch a single result for gql subscriptions
* removed unused import
---------
Co-authored-by: Rijk van Zanten <rijkvanzanten@me.com>
* 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>