Feature/labelspaces #30
Merged
Conversation
This file contains 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
nathanhhughes
force-pushed
the
feature/flexible_layer
branch
from
483fecf to
f06ad91
Compare
nathanhhughes
force-pushed
the
feature/labelspaces
branch
from
5bfee58 to
8708dd8
Compare
nathanhhughes
force-pushed
the
feature/labelspaces
branch
from
eaab6f2 to
17f7499
Compare
GoldenZephyr
approved these changes
Feb 14, 2025
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.
Updates the metadata API slightly and formalizes the API around a labelspace to avoid json forcing the weird string keys for integer labels. Mostly just staging this for when
feature/flexible_layeractually gets merged. @Schmluk mostly adding you in case you're interested but anticipate @GoldenZephyr actually doing the review