* 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>
* broken migration
* fixed migration
* created new endpoints for translation strings
* updated to use core endpoint
* bad attempts at making the endpoints sensible
* merge changes
* implemented translation strings service
* re-integrating app logic part 1
* re-integrating app logic part 2
* fixed bad lodash import
* re-integrating app logic part 3
* removed obsolete tests
* make the linter happy
* Create tender-trees-buy.md
* added option to search-input
* implementing search
* fixed resizing and sidebar
* Fix linting
* Remove unused translations update into project settings
* Fix missing translations
* Require read permissions for app access
* Fetch translation strings only when authenticated
* Fix project default language not used when user has default language
* Remove commented line
* Rename variable as content has been changed
* Make the current user check more specific
* Remove translation_string from Settings type
* Remove settings reference in docs
* Update changeset
* Rename migration file to ensure date order
* Rename collection, route, service, controller
* Rename migration
* Adjust collection in settings route
* Fix translations service
* Use new `shouldClearCache` util
* Drop translation_strings column in migration
Co-authored-by: ian <licitdev@gmail.com>
* Added basic api docs
* updated dictionary
* updated dictionary
* Update app/src/interfaces/_system/system-input-translated-string/input-translated-string.vue
Co-authored-by: Nicola Krumschmidt <nicola.krumschmidt@freenet.de>
* Update app/src/modules/settings/routes/translation-strings/collection.vue
Co-authored-by: Nicola Krumschmidt <nicola.krumschmidt@freenet.de>
* extracted getCurrentLanguage utility
* Use regular collections/items
* Use regular controller
* Fix item view
* Set correct system field config for translations
* Tweaks
* Use UUID
* Finish placeholders
* Use drawer-item
* Add create to the store
* Remove composables
* Add new placeholder
* Fix saving behavior
* Remove previous take
* Rename migration after merge of live preview
* Generate uuid when migrating
* Remove unused showFilter
* Fix linting
* Fix type warnings
* Not needed as settings no longer contain translation_strings
* Remove leftover blank line
* Update getCurrentLanguage with server default and use in hydrate
* Shift getCurrentLanguage to lang folder to be alongside setLanguage
* add elipsis to placeholder
* Remove slug from key, so you can use dots etc in the key
* updated translation value to be type text again
* Rehydrate fields for updated translation values
* Add tooltip
* updated documentation
* enforce key/language uniqueness in the TranslationService
* updated error message
* updated docs menu item to "custom translations"
* Dynamically fetch translation keys for input-translated-string interface
* use get current language in refresh
* Update docs/reference/system/translations.md
* Update docs/reference/system/translations.md
* Update .changeset/tender-trees-buy.md
* Fetch translation keys when new key is created
* Update api/src/services/translations.ts
* Remove translation_strings remnant
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
* mark key, language and value as required
* correctly mark fields as required
* Catch duplicate key error when creating from input
* Translate translations :-)
* Update tender-trees-buy.md
---------
Co-authored-by: ian <licitdev@gmail.com>
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
Co-authored-by: Nicola Krumschmidt <nicola.krumschmidt@freenet.de>
Co-authored-by: rijkvanzanten <rijkvanzanten@me.com>
* Prevent auto conversion of png to jpg images
* Create red-swans-march.md
* Update transformation tests
* Update blackbox test
* Fix image allocation
* Fix test again :-)
* Convert formats with transparency support to png (if no accept header)
* Update tests & add final fallback
* Update changeset
* Update blackbox test
---------
Co-authored-by: rijkvanzanten <rijkvanzanten@me.com>
* Adding a maximum for query limit
* fixed bad env check
* using the getEnv function to make it better testable
* updated sanitize-query tests
* added tests for the validate query function
* Added DEFAULT_QUERY_LIMIT as fallback instead
* make the linter happy
* accept infinity as max_query_limit
* fixed merge conflicts
* added missing import
* moved docs PR into main repo
* added missing import
* renamed vars
* basic page size limiting
* Update app/src/layouts/cards/cards.vue
* Update app/src/layouts/map/map.vue
* Update app/src/layouts/tabular/tabular.vue
* Update app/src/layouts/tabular/tabular.vue
* Create paginate util
* extracted page size logic to composable and implemented default usage in app
* updated paginate utility
* using the new fetch-all utility
* removed limit: -1 for api calls that do not support it
* fix linter
* removed console log
* making the linter happy
* Create loud-flowers-yawn.md
* Add tests for no / unlimited limit
* Cover all cases for max limit in sanitizeQuery
* Get rid of non-null assertion
* added test for composable
* Update var names in documentation
* replace hardcoded limit default with env var
* update default page size behavior
* fixed test
* update server info api reference
* include queryLimit in graphql server info
* use configured max limit in calendar layout
* use configured max limit in kanban layout
* account for max query limit in use-revisions
---------
Co-authored-by: ian <licitdev@gmail.com>
Co-authored-by: rijkvanzanten <rijkvanzanten@me.com>
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
Co-authored-by: Azri Kahar <42867097+azrikahar@users.noreply.github.com>
* Support for re-sending user invites. Close#1799
* Reuse getUserByEmail in user service.
* Add mockImplementation to spies on ItemsServices
* Signed contributors list.
* Fix invite tests
* Fix comments
---------
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
Co-authored-by: Rijk van Zanten <rijkvanzanten@me.com>
* Fix too many SQL Variables
* run linter
* Use lodash' chunk instead of custom for loop
---------
Co-authored-by: Rijk van Zanten <rijkvanzanten@me.com>
* Adds ability to verify JWT with meaningful errors
* Fix tests
* Apply verify JWT to accept invitation
* Update per review
* Add joselcvarela to contributors
He's a core team member; already signed the CLA outside of GH
---------
Co-authored-by: Brainslug <br41nslug@users.noreply.github.com>
Co-authored-by: rijkvanzanten <rijkvanzanten@me.com>
* Step 1
* Step 2
* False sense of confidence
* Couple more before dinner
* Update schema package
* Update format-title
* Upgrade specs file
* Close
* Replace ts-node-dev with tsx, and various others
* Replace lodash with lodash-es
* Add lodash-es types
* Update knex import
* More fun is had
* FSE
* Consolidate repos
* Various tweaks and fixes
* Fix specs
* Remove dependency on knex-schema-inspector
* Fix wrong imports of inspector
* Move shared exceptions to new package
* Move constants to separate module
* Move types to new types package
* Use directus/types
* I believe this is no longer needed
* [WIP] Start moving utils to esm
* ESMify Shared
* Move shared utils to @directus/utils
* Use @directus/utils instead of @directus/shared/utils
* It runs!
* Use correct schemaoverview type
* Fix imports
* Fix the thing
* Start on new update-checker lib
* Use new update-check package
* Swap out directus/shared in app
* Pushing through the last bits now
* Dangerously make extensions SDK ESM
* Use @directus/types in tests
* Copy util function to test
* Fix linter config
* Add missing import
* Hot takes
* Fix build
* Curse these default exports
* No tests in constants
* Add tests
* Remove tests from types
* Add tests for exceptions
* Fix test
* Fix app tests
* Fix import in test
* Fix various tests
* Fix specs export
* Some more tests
* Remove broken integration tests
These were broken beyond repair.. They were also written before we really knew what we we're doing with tests, so I think it's better to say goodbye and start over with these
* Regenerate lockfile
* Fix imports from merge
* I create my own problems
* Make sharp play nice
* Add vitest config
* Install missing blackbox dep
* Consts shouldn't be in types
tsk tsk tsk tsk
* Fix type/const usage in extensions-sdk
* cursed.default
* Reduce circular deps
* Fix circular dep in items service
* vvv
* Trigger testing for all vendors
* Add workaround for rollup
* Prepend the file protocol for the ESM loader to be compatible with Windows
"WARN: Only URLs with a scheme in: file and data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'"
* Fix postgres
* Schema package updates
Co-authored-by: Azri Kahar <42867097+azrikahar@users.noreply.github.com>
* Resolve cjs/mjs extensions
* Clean-up eslint config
* fixed extension concatination
* using string interpolation for consistency
* Revert MySQL optimisation
* Revert testing for all vendors
* Replace tsx with esbuild-kit/esm-loader
Is a bit faster and we can rely on the built-in `watch` and `inspect`
functionalities of Node.js
Note: The possibility to watch other files (.env in our case) might be
added in the future, see https://github.com/nodejs/node/issues/45467
* Use exact version for esbuild-kit/esm-loader
* Fix import
---------
Co-authored-by: ian <licitdev@gmail.com>
Co-authored-by: Brainslug <tim@brainslug.nl>
Co-authored-by: Azri Kahar <42867097+azrikahar@users.noreply.github.com>
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
* add rate limiter, rate limiter global and flows
* fix project fields in server info
* add graphql for /utils/random/string
---------
Co-authored-by: Rijk van Zanten <rijkvanzanten@me.com>
