Add mobile-ui version labels to the docs - #544
Merged
Merged
Conversation
The EDGE components ship in nativephp/mobile-ui, which has its own release line, so the docs version badge had no way to say a feature needs a newer mobile-ui. The badge now takes a package attribute, backed by a docs.packages config entry, and 20 labels mark what arrived after 0.3, the release current when mobile 4.0.0 shipped. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
The EDGE components ship in
nativephp/mobile-ui, which has its own release line (0.1 to 0.7). The docs version badge only understood NativePHP for Mobile versions, so there was no way to say a component or prop needs a newer mobile-ui.<x-docs.version-badge>now takes apackageattribute:For a whole page, use
package: mobile-uiandsince: "0.6"in the front matter. The pill reads "mobile-ui 0.6", the tooltip namesnativephp/mobile-ui, and it links to a new "mobile-ui labels" section on the versioning page. That section also covers the upgrade catch: Composer's^0.5never installs 0.6, so you have to raise the constraint and rebuild.Package details live in a new
docs.packagesconfig entry. Labels at or below 0.3 don't render, because 0.3 was current when mobile 4.0.0 shipped. That mirrors how x.0 never renders for core labels.Labels added
20 labels across 7 pages. Each one was traced to the code at the mobile-ui tags, because the GitHub release notes turned out to be unreliable for this.
autocapitalizeand the capitalization rules (0.5).native:font: changed in 0.4, when its options were reworked, plus the three options it gained.Nothing documented needed a 0.6 or 0.7 label. Those releases were bug fixes or features that aren't documented yet.
Tests
The guard test now checks package labels against the package's own released versions and flags unknown packages. It also rejects unquoted versions in front matter. YAML reads
since: 0.10as the number 0.1, and the old check accepted that.Things to check
docs.packages.mobile-ui.released_versionsbefore using it in a label, or the guard test fails.🤖 Generated with Claude Code