Repository navigation
docs: connect tool choice with the public snapshot API - #17
Merged
Merged
Conversation
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.
Readers could run the invoice example but had no short route from that example to tool selection and API reuse. Add a single guide linked from both READMEs, describing PITBridge's local inspection task alongside SQL, pandas and Feast, and listing the existing public inputs, snapshot return structure and error boundaries.
The guide cites official contracts, including Feast's created-timestamp filtering, and does not claim a cross-tool performance or correctness result. It identifies the inspected source snapshot without promising cross-version compatibility. Update the contribution list to improve the existing CSV adapter rather than invite a duplicate implementation.
Validation: 56 local references/anchors checked; public signatures and snapshot fields inspected; the original invoice example and SQL/reference/expected selections pass. Independent review confirmed the API and cited time semantics. Runtime code and dependencies are unchanged.