Repository navigation
docs: make the first Java trace runnable and verifiable - #38
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
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.
First-time users can now run a complete Java example from the README using the published 0.2.3 core artifact and Langfuse project keys. It sends fixed synthetic content, verifies three observations and their parent links through Observations API v2, and prints a trace URL. No model API key or local library install is required.
The README includes an actual Langfuse screenshot with its matching read-back JSON and provenance. A bilingual installation-feedback issue form and ready-to-review community introduction drafts provide a public feedback path. No external outreach has been posted and no external adoption is claimed.
Validation:
Library behavior and release version are unchanged. The example POM intentionally tracks the published release separately from the reactor development version. Local Docker was out of space; live verification used disposable GitHub-hosted infrastructure, and existing Docker data was not removed.