docs(readme): bump to 0.75.0 + document v0.73-v0.75 PXF API additions#40
Merged
Conversation
The README's install snippets and version banner still pointed at 0.70.0, and the PXF API section covered unmarshal / unmarshalFull / marshal / parse but stopped at v0.72. Five public-API surfaces landed between v0.73 and v0.75 with no README footprint: - Result.directives() / Result.tables() — @<name> + @table capture on unmarshalFull (v0.73) - TableReader over InputStream — streaming @table consumption bounded by largest single row (v0.74) - TableReader.scan(Message.Builder) / BindRow.bindRow — per-row proto binding sugar (v0.75) - SchemaValidator.validateFile / validateDescriptor + UnmarshalOptions.withSkipValidate — schema reserved-name check (v0.73) Adds four subsections under "PXF API": - Directives and @table (Result accessors): worked example iterating r.directives() + r.tables() with the three-state cell contract spelled out. - TableReader: streaming @table consumption: InputStream → row iterator + tail() for multi-table chaining + per-row error semantics. - scan and BindRow: per-row binding: both APIs with the same cell-state contract; WKT + wrapper + enum semantics noted. - Schema reserved-name check: SchemaValidator + withSkipValidate opt-out + case-sensitivity callout. Updates the Feature coverage list with six new ✅ items covering the new surfaces. All four narrative sections link back to the spec sections (§3.4.4 streaming note, §3.13 reserved-name rule). Install snippets (Maven + Gradle) bumped 0.70.0 → 0.75.0.
trendvidia
added a commit
that referenced
this pull request
May 12, 2026
CodeQL was failing with "could not process any code written in Java/Kotlin" on PRs that touched no Java source — the README PR (#40) and the release-cut commit (#39, which only edits CHANGELOG.md). Diagnosis: gradle/actions/setup-gradle@v6 restores the build cache on every run. README- and CHANGELOG-only changes leave every input to the JavaCompile task identical, so Gradle reports the `classes` task as UP-TO-DATE and runs zero `javac` invocations. CodeQL's Java tracer wraps `javac`; no invocations means no extracted classes, which surfaces as the empty-database error at the analyze step. Confirmed by the run-duration pattern in `gh run list --workflow=codeql.yml`: - failing runs (#39 release-cut, #40 README) finished in ~1 min - successful runs (#35-#38 feature PRs that touched src/) took ~2 min The minute of "missing" wall-clock is exactly the javac step that didn't run. Fix: `--no-build-cache clean classes` forces a recompile every CodeQL invocation. Drops a `clean` task ahead of `classes` to guarantee no UP-TO-DATE skip, and `--no-build-cache` is belt-and-braces against the setup-gradle action's cache restore. Slightly slower CodeQL runs (~30s more on cold compile) but the analyze step gets real javac output to extract from.
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.
Summary
The README's install snippets and version banner still pointed at `0.70.0`, and the PXF API section covered `unmarshal` / `unmarshalFull` / `marshal` / `parse` but stopped at v0.72. Five public-API surfaces landed between v0.73 and v0.75 with no README footprint:
What's added
All four narrative sections link back to the spec sections (§3.4.4 streaming note, §3.13 reserved-name rule).
Test plan