docs: ease the landing examples into the API - #375
Merged
Conversation
The SQL template belongs later in the journey than the landing page and the README opener: it is the escape hatch, not the first impression. The intro sequence now ends at the query builder, and the Kotlin example uses the chained builder rather than the block DSL.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes the SQL-template example from the introductory sequences in
docs/index.md(both language tabs) andREADME.md— the escape hatch comes too soon at that point in the journey; the dedicated SQL Templates page is unchanged. The Kotlin landing example now uses the chained builder (select().where(...).orderBy(...)) instead of the block DSL, matching the Java tab.