docs(datasources): surface native joins for discoverability + REST/JS…#277
Merged
Conversation
… key parity (DEV-1360)
Make Fliplet Data Source joins discoverable to the V3 AI builder and accurate
across the JS and REST references, so the builder reaches for the native
find({ join }) API instead of fetching both sources and matching in JS.
- fliplet-datasources.md: add join/joins/related-data/combine-data-sources/
lookup/relationship to `capabilities:` (the V3 catalog uses these to map
user intent -> API technique); add an early pointer from the find() docs to
the joins section; make the joins section self-contained with a worked
find({ join }) example. Joined data is accessed at result[i].join.X
(sibling of .data), not result[i].data.X.
- joins.md: clarify the JS API returns matches under `join` (singular) while
the REST endpoint returns `joins` (plural); note order+limit is global-order
then per-parent limit. (verified against routes/v1/data-sources.js)
- REST-API/fliplet-datasources.md: add a "Joining data from another data
source" subsection to /data/query with request/response example.
- Regenerate .well-known (llms-v3-libraries.json now advertises join
capabilities; llms-full.txt reflects the joins doc edits).
Pairs with the Studio builder.md directive (DEV-1360) that mandates native
joins; this side makes the technique discoverable + correct in the docs.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Deploying fliplet-cli with
|
| Latest commit: |
21a407a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://eceee9ff.fliplet-cli.pages.dev |
| Branch Preview URL: | https://fix-ai-docs-md-urls.fliplet-cli.pages.dev |
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.
… key parity (DEV-1360)
Make Fliplet Data Source joins discoverable to the V3 AI builder and accurate across the JS and REST references, so the builder reaches for the native find({ join }) API instead of fetching both sources and matching in JS.
capabilities:(the V3 catalog uses these to map user intent -> API technique); add an early pointer from the find() docs to the joins section; make the joins section self-contained with a worked find({ join }) example. Joined data is accessed at result[i].join.X (sibling of .data), not result[i].data.X.join(singular) while the REST endpoint returnsjoins(plural); note order+limit is global-order then per-parent limit. (verified against routes/v1/data-sources.js)Pairs with the Studio builder.md directive (DEV-1360) that mandates native joins; this side makes the technique discoverable + correct in the docs.