jdaugherty opened a new pull request, #16794: URL: https://github.com/apache/grails-core/pull/16794
GraphQL has been a Forge feature since 7.2.x (`gorm-graphql`, category API), but it is harder to find and use than it should be. The README of a generated application only linked to graphql.org, the command line reference never listed the feature, the Grails Data GraphQL manual was not staged with the other Grails Data manuals, so the documentation URL the plugin descriptor and README declare 404s on every published docs version, the Grails Data documentation index still said the library had not been ported to Grails 7, and its installation page pointed at the pre-Apache `gorm-graphql-plugin` coordinates. This links the feature to the Grails Data GraphQL manual of the generated Grails version, the way the other Grails Data features do; lists `gorm-graphql` in the create-app and create-restapi references and in the `--list-features` sample output (the feature is not offered for plugins, so those references are unchanged); stages the manual under `grails-data/graphql/manual` next to the Hibernate and MongoDB manuals and links it from the Grails Data index; and points the installation page at `org.apache.grails:grails-data-graphql` and the Forge feature. Tests cover the feature through the APIs Forge UI and the CLI use: the available features of each application type, the feature list served by the HTTP API, the generated `build.gradle` and README, and that a `gorm=MONGODB` selection keeps MongoDB rather than falling back to Hibernate. Verified in `grails-forge` with the full `grails-forge-core` and `grails-forge-api` test suites and `./gradlew codeStyle`, and at the root with `:grails-data-docs-stage:copyGraphqlDocs`, which produces the manual with the install snippet rendered for the current version. The documentation link starts resolving once the next docs publish includes the staged output; until then it 404s as it did before. Background, since there is no issue for this: the question came up because GraphQL does not appear in the Forge UI's feature picker for the PREV and OLDER channels. Those run 7.1.x and 7.0.x, where `grails-data-graphql` is not part of the build and no artifact is published, so a feature there would generate a build that cannot resolve. That is out of scope here. Merges up through 8.0.x, 8.1.x, 9.x and 10.x; 8.1.x needs a hand port of the two small source changes because the Forge moved to Groovy and Spring on that line. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
