The piece in the docs regarding adding a value to the list of common languages is not valid anymore.
SS4 uses the php-intl extension, so before adding an extra locale, the user needs to check whether the installed ICU lib on the server supports it.
If that is the case, the locale can added through the config system by adding a piece of yaml.
* DOCS: Add new graphql 4 docs
* Reorganise docs
* Docs done
* Basic graphql index page
* TOC for getting started
* show folders on graphql index page
* Add middleware note
* Docs update
* Update docs to reflect flushless schema
* Docs updates
* Docs for getByLink
* Query caching docs
* Docs on nested operations
* update docs for new graphql dev admin
* Docs for configurable operations
* Replace readSiteTrees with readPages
* Schema defaults docs
* Docs for inherited plugins
* Docs for customising *
* Docs for field whitelisting
* Change whitelist word
* New docs on modelConfig
* Document dev/build extension
* Document default/global plugins
* Document new input type fields config
* Apply suggestions from code review
Co-authored-by: Andre Kiste <bergice@users.noreply.github.com>
* Note about when procedural schema gets built
* Fix link
* Apply suggestions from code review
Co-authored-by: Andre Kiste <bergice@users.noreply.github.com>
* Apply suggestions from code review
Co-authored-by: Andre Kiste <bergice@users.noreply.github.com>
* DOCS Note about plugins in custom queries
* DOCS Note about filter and custom resolvers
* DOCS Note about canview paging
* DOCS Updated guidance on _extend
See https://github.com/silverstripe/silverstripe-graphql/issues/296
* Apply suggestions from code review
Co-authored-by: Andre Kiste <bergice@users.noreply.github.com>
* DOCS Pre-release warning
Co-authored-by: Ingo Schommer <ingo@silverstripe.com>
Co-authored-by: Andre Kiste <bergice@users.noreply.github.com>
Co-authored-by: Ingo Schommer <me@chillu.com>
Note that it's currently unclear whether Silverstripe Cloud or CWP support this,
but it shouldn't block us from recommend this in the open source project.
It's documented in the "server requirements", which should make it pretty
clear that this requires you to have control over server configuration (or check with those that have).
See https://github.com/silverstripe/silverstripe-framework/issues/7710
DOC HistoryViewer: explain "magic names"
GraphQL scaffolding uses names consisting of the first part of the namespace and the classname, but to inject it to the HistoryViewer field you need to use the database table name.
Co-authored-by: Steve Boyd <emteknetnz@gmail.com>
- create a new documentation section explaining the "cached" block
- clean up the Performance documentation section,
moving explanations about "cached" block away,
adding new warnings and recommendations
* #3236 Added dev/config view
* Refactored use of echo to
* Added config/audit for matching missing property definitions in the current config
* Minor enhancements to dev/config implementation
