* DOCS Clearer sysadmin guidance for "packaging"
We have all kinds of fun fallbacks that attempt to create supporting files in production environments.
The latest point of contention is dev/build automatically creating files in .graphql/ and public/_graphql/
if those don't exist. That should be regarded as a last resort option to allow introduction of GraphQL v4 in the CMS 4.x release line.
At least since CMS 4.1, we need some form of "packaging" for generated files (public/_resources),
or committing these into the codebase, so let's call that out for anyone running CMS infra.
* Add trailing slash
Co-authored-by: Aaron Carlino <unclecheese@leftandmain.com>
- I believe the YAML file should be included for the completeness of this example.
- Added details on Caching, I know this is duplication, but I believe it reinforces this requirement by example.
- The example **phpunit.xml** file is a basic working example.
I propose this as a more complete how-to, my thinking is someone new reading this how-to documentation, can follow the instructions and successfully run the example test. I hope this is acceptable.
- The Silverstripe 4 folder structure has been changed from **app/code/** to **app/src/**
- Renamed Silverstripe in text. I assume `api:` and `Namespace`, should remain SilverStripe
- Added some missing semicolons
The link to the api documentation for `writeWithoutVersion()` was invalid and not rendering as a link. Also fixed a couple of typos in surrounding text.
It appears there may be a bug in gatsby which causes code blocks in headings to not be output. I can't find a specific issue in their project to link this to, so it might be best to simply remove the code block here allowing the header to display correctly.
Otherwise the code is output as html, and displays as a missing image. The alt attribute is required for image tags, whereas self closing is no longer required for html5.
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
