Pydantic package organization episode 1: "Making huge mess" by vcschapp · Pull Request #397 · OvertureMaps/schema

Victor Schappert (vcschapp) · 2025-10-03T00:17:36Z

tl;dr

This is part #1 only. Part #2 will follow fast.

Yes, it leaves things in a mess (temporarily). This is mainly to produce a manageable diff and let us get some alignment on the destination.

Let's ship this quickly so the process doesn't bog down. The end goal is a full and final organization of the packages and the end of churn.

Destination

Packages.
- ▶️ The package setup will be organized as diagrammed below.
- ⬜️ Package dependencies and pyproject.toml will be standardized.
Documentation.
- ✅ All doctests will pass and automatically be enforced to pass by make check.
- ▶️ All documentation will pass pydocstyle with the NumPy convention. (As of now, the tool reports too many complaints to add it into make check.)
- ⬜️ pydocstyle will be enforced by make check.
- ⬜️ docformatter will be run by make check.
- ⬜️ Package-level README content will migrate into the package's __init__.py docstring.
- ⬜️ There will be a doc target in the Makefile that does uv run pdoc to a useful place.
- ⬜️ Our most foundational BaseModel base class in system will be given an optional description property that can be used to provide class-level documentation for the schema user persona. (See this conversation in the comments on this PR.)
Modules.
- ▶️ Re-exports will be standardized and everything of value will be re-exported into the main module.
- ⬜️ In theme packages, the primary module will be feature, which will contain the feature models and the main simple types that support them.
- ⬜️ In theme packages, if a field contains a theme-specific "deep model" then it will be given its own module, e.g. perspectives.

Packaging Deep Dive

The target layout is as shown below.

overture-schema-system

The system package is at the base of the pyramid, and will contain the stuff, otherwise known as "George", that is maximally reusable in any data modeling environment, not just Overture.

The name system was chosen after some reflection to try to symbolize something "more basic than core".
The previous name candidate, foundation, has the unfortunate characteristic of being part of the name Overture Maps Foundation, so was dropped.
Much of the validation package will end up in system, but some will also migrate up into core.
Some of the core package will migrate down into system.

overture-schema-core

The core package contains the shared types that are specific to Overture data. It will continue more or less unchanged, but some of its contents will migrate down to system.

overture-schema-annex

The annex package will contain "all the other Overture schemas" part from the main geospatial data. The content from the sources package will move in here.

overture-schema-***-theme

The theme packages will remain as-is, subject to:

Module standardization.
Documentation standardization.

#397 (comment) The proximate issue was that BSD `sed` on MacOS doesn't support alternation unless you use `-E`. But also the alternation wasn't needed, so I removed it.

This commit used to move "sources" out of the way for now, but that's over now after rebasing on Seth's #394.

…and TrimmedString -> StrippedString (stripped = Python term, not trim)

…yet... ...Too many broken docs to bother

…kages

…n" overload

#397 (comment) The proximate issue was that BSD `sed` on MacOS doesn't support alternation unless you use `-E`. But also the alternation wasn't needed, so I removed it.

#397

-#397 (comment)

Re-org. Pydantic packages (2/N) The destination is as described in PR #397 (1/N) and PR #400. In this commit, the following value is added: 1. 🐞 Fix bug: The `@any_of` decorator was not working with transporation destinations. The bug was discovered while refactoring the `mixin` module and the fix is reflected in the updated transportation schema baseline. 2. 🐞 Fix bug: The `make doctest` target exited with code 0 (success) even if it found doctest failures. This bug was added in #397 when the `doctest` target was added and is now fixed. 3. Apply multiple suggestions from PR #397 including renaming `CountryCode` to `CountryCodeAlpha2` and dropping an unnecessary attribute from `PatternConstraint`. 4. Rename the sources package to annex in alignment as shown in the destination package diagram. 5. Begin refactoring `mixin` module to fix some known issues and polish it for final release. Changes made here: - Underlying implementation is replaced with the Pydantic function `create_model` (as was done in the scoping POC) which eliminates the need for `ConstrainedBaseModel` and should also eliminate MRO issues. - Underlying implementation uses some basic "JSON Schema algebra" to ensure that multiple decorators can coexist without breaking each others' JSON Schema changes. - The module name `mixin` is replaced by `model_constraint`, which feels more use case-oriented. - Initially one main decorator is migrated from `mixin` in the validation package to `model_constraint` in the system package. The rest will come next PR. 6. Migrate much of the validation package `README.md` into the system package's main module `__init__.py` and migrate the examples into doctests. 7. Re-home a few other bits of functionality from validation to core. 8. Bring the https://github.com/vcschapp/overture-schema-pydantic scoping into core as `scoping.py` and fix up the linter errors. This is not wired up yet, but that's Coming Soon, likely in episode 4. 9. At Seth's suggestion, switch `ConfidenceScore` from `float64` to `float32` though we will have to double-check the actual value in the Parquet model here. Stay tuned for episode 3, where we will finish re-homing the validation package.

The destination is as described in PR #397 (1/N), PR #400, and PR #403. In this commit, the following value is added: 1. 🐞 Fix bug: The `not_required_if` mixin wasn't meeting the original schema intent, which result in the `DivisionBoundary` feature type having the wrong JSON Schema. The expected behavior is "if the boundary is at the country level, then the `country` pair should be omitted" but instead it did two variations: in the Python validator, it required the country pair to be present; and in the JSON Schema, it required the country pair to be present, but only if the condition was not true. Both were subtly wrong. The bug is fixed in this commit and the mixin is renamed to `forbid_if`, which I hope will make the semantics more obvious. 2. 🐞 Fix bug: Very subtle, but the mixin model constraint validators did not work correctly if added directly to a `Feature` model, because they aren't aware of the quirky multi-tiered GeoJSON JSON Schema where most properties get pushed down into "properties", but some do not. This is (hopefully ... 🤞) fixed in the new `Feature` model in the system package. 3. 🐞 Fix bug: Very subtle, but the previous `Feature` model's JSON Schema did not prohibit fields named `"id"`, `"bbox"`, and `"geometry"` within the properties object. This created a weird quirk where in a poisoned JSON object containing those values under properties, the properties version would overwrite the root version. This is fixed by explicitly prohibiting those fields in the JSON Schema for the `Feature` class' properties object. 4. 🐞 Fix bug: The `ExtensibleBaseModel`'s `patternProperties` got put both at the top level of the GeoJSON Feature schema and in the "properties" object schema. This would have allowed the input JSON to contain `ext_*` at two levels, which doesn't meet the original schema intent. As part of this bug fix, `ExtensibleBaseModel` is collapsed directly into `OvertureFeature` and the `ext_*` feature is documented as being on a deprecation path. 5. The `validation` package is officially deleted as its essential George functions have all been re-homed either into `system` or `core`. 6. All model constraint mixins have been refactored along the lines started in PR #400. They are now called `@forbid_if`, `@min_fields_set`, `@no_extra_fields`, `@radio_group`, `@require_any_of`, and `@require_if`. 7. A type hint, `Omitable[T]` has been added to the system package. This type hint allows a Pydantic model to "naturally" get JSON Schema semantics for omitted values - it de-conflates optionality and nullability, which Pydantic currently conflates. In an upcoming episode, I hope to replace the `X | None` unions in the existing model with `Omitable[X]`. 8. The existing `Feature` class from the `core` package has been split into two: (i) `Feature` in the `system` package now acts as a generic feature and owns all the funky GeoJSON logic, allowing George enthusiasts to work with a nice ergonomic feature type without having to use an "Overture"-flavored feature; (ii) `OvertureFeature` in the `core` package adds the Overture schema specific flavoring on top of `Feature`. 9. The `ref` module from `core` has been pushed down into `system` and the dependency on `(Overture)Feature` has been factored out in favor of a generic dependency on an `Identified` model, which is basically just a `BaseModel` with a mandatory ID. Stay tuned for episode 4, where we will re-organize the core package.

The destination is as described in PR #397. In this commit, the following initial steps are taken: 1. Introduce the `system` package and begin migrating the lowest- level building blocks into it from `validation` and `core`. 2. Begin standardizing the Python module approach in a way that will result in fairly ergonomic API reference docs generated by `pdoc`. 3. Fix all broken doctests and include doctests in `make check`. 4. Add a make target for `pydocstyle` with the goal to eventually add it into `make check`. 5. Some renaming and re-organization of types. Stay tuned for episode 2, coming soon to a GitHub near you.

Re-org. Pydantic packages (2/N) The destination is as described in PR #397 (1/N) and PR #400. In this commit, the following value is added: 1. 🐞 Fix bug: The `@any_of` decorator was not working with transporation destinations. The bug was discovered while refactoring the `mixin` module and the fix is reflected in the updated transportation schema baseline. 2. 🐞 Fix bug: The `make doctest` target exited with code 0 (success) even if it found doctest failures. This bug was added in #397 when the `doctest` target was added and is now fixed. 3. Apply multiple suggestions from PR #397 including renaming `CountryCode` to `CountryCodeAlpha2` and dropping an unnecessary attribute from `PatternConstraint`. 4. Rename the sources package to annex in alignment as shown in the destination package diagram. 5. Begin refactoring `mixin` module to fix some known issues and polish it for final release. Changes made here: - Underlying implementation is replaced with the Pydantic function `create_model` (as was done in the scoping POC) which eliminates the need for `ConstrainedBaseModel` and should also eliminate MRO issues. - Underlying implementation uses some basic "JSON Schema algebra" to ensure that multiple decorators can coexist without breaking each others' JSON Schema changes. - The module name `mixin` is replaced by `model_constraint`, which feels more use case-oriented. - Initially one main decorator is migrated from `mixin` in the validation package to `model_constraint` in the system package. The rest will come next PR. 6. Migrate much of the validation package `README.md` into the system package's main module `__init__.py` and migrate the examples into doctests. 7. Re-home a few other bits of functionality from validation to core. 8. Bring the https://github.com/vcschapp/overture-schema-pydantic scoping into core as `scoping.py` and fix up the linter errors. This is not wired up yet, but that's Coming Soon, likely in episode 4. 9. At Seth's suggestion, switch `ConfidenceScore` from `float64` to `float32` though we will have to double-check the actual value in the Parquet model here. Stay tuned for episode 3, where we will finish re-homing the validation package.

The destination is as described in PR #397 (1/N), PR #400, and PR #403. In this commit, the following value is added: 1. 🐞 Fix bug: The `not_required_if` mixin wasn't meeting the original schema intent, which result in the `DivisionBoundary` feature type having the wrong JSON Schema. The expected behavior is "if the boundary is at the country level, then the `country` pair should be omitted" but instead it did two variations: in the Python validator, it required the country pair to be present; and in the JSON Schema, it required the country pair to be present, but only if the condition was not true. Both were subtly wrong. The bug is fixed in this commit and the mixin is renamed to `forbid_if`, which I hope will make the semantics more obvious. 2. 🐞 Fix bug: Very subtle, but the mixin model constraint validators did not work correctly if added directly to a `Feature` model, because they aren't aware of the quirky multi-tiered GeoJSON JSON Schema where most properties get pushed down into "properties", but some do not. This is (hopefully ... 🤞) fixed in the new `Feature` model in the system package. 3. 🐞 Fix bug: Very subtle, but the previous `Feature` model's JSON Schema did not prohibit fields named `"id"`, `"bbox"`, and `"geometry"` within the properties object. This created a weird quirk where in a poisoned JSON object containing those values under properties, the properties version would overwrite the root version. This is fixed by explicitly prohibiting those fields in the JSON Schema for the `Feature` class' properties object. 4. 🐞 Fix bug: The `ExtensibleBaseModel`'s `patternProperties` got put both at the top level of the GeoJSON Feature schema and in the "properties" object schema. This would have allowed the input JSON to contain `ext_*` at two levels, which doesn't meet the original schema intent. As part of this bug fix, `ExtensibleBaseModel` is collapsed directly into `OvertureFeature` and the `ext_*` feature is documented as being on a deprecation path. 5. The `validation` package is officially deleted as its essential George functions have all been re-homed either into `system` or `core`. 6. All model constraint mixins have been refactored along the lines started in PR #400. They are now called `@forbid_if`, `@min_fields_set`, `@no_extra_fields`, `@radio_group`, `@require_any_of`, and `@require_if`. 7. A type hint, `Omitable[T]` has been added to the system package. This type hint allows a Pydantic model to "naturally" get JSON Schema semantics for omitted values - it de-conflates optionality and nullability, which Pydantic currently conflates. In an upcoming episode, I hope to replace the `X | None` unions in the existing model with `Omitable[X]`. 8. The existing `Feature` class from the `core` package has been split into two: (i) `Feature` in the `system` package now acts as a generic feature and owns all the funky GeoJSON logic, allowing George enthusiasts to work with a nice ergonomic feature type without having to use an "Overture"-flavored feature; (ii) `OvertureFeature` in the `core` package adds the Overture schema specific flavoring on top of `Feature`. 9. The `ref` module from `core` has been pushed down into `system` and the dependency on `(Overture)Feature` has been factored out in favor of a generic dependency on an `Identified` model, which is basically just a `BaseModel` with a mandatory ID. Stay tuned for episode 4, where we will re-organize the core package.

The destination is as described in PR #397. In this commit, the following initial steps are taken: 1. Introduce the `system` package and begin migrating the lowest- level building blocks into it from `validation` and `core`. 2. Begin standardizing the Python module approach in a way that will result in fairly ergonomic API reference docs generated by `pdoc`. 3. Fix all broken doctests and include doctests in `make check`. 4. Add a make target for `pydocstyle` with the goal to eventually add it into `make check`. 5. Some renaming and re-organization of types. Stay tuned for episode 2, coming soon to a GitHub near you.

Re-org. Pydantic packages (2/N) The destination is as described in PR #397 (1/N) and PR #400. In this commit, the following value is added: 1. 🐞 Fix bug: The `@any_of` decorator was not working with transporation destinations. The bug was discovered while refactoring the `mixin` module and the fix is reflected in the updated transportation schema baseline. 2. 🐞 Fix bug: The `make doctest` target exited with code 0 (success) even if it found doctest failures. This bug was added in #397 when the `doctest` target was added and is now fixed. 3. Apply multiple suggestions from PR #397 including renaming `CountryCode` to `CountryCodeAlpha2` and dropping an unnecessary attribute from `PatternConstraint`. 4. Rename the sources package to annex in alignment as shown in the destination package diagram. 5. Begin refactoring `mixin` module to fix some known issues and polish it for final release. Changes made here: - Underlying implementation is replaced with the Pydantic function `create_model` (as was done in the scoping POC) which eliminates the need for `ConstrainedBaseModel` and should also eliminate MRO issues. - Underlying implementation uses some basic "JSON Schema algebra" to ensure that multiple decorators can coexist without breaking each others' JSON Schema changes. - The module name `mixin` is replaced by `model_constraint`, which feels more use case-oriented. - Initially one main decorator is migrated from `mixin` in the validation package to `model_constraint` in the system package. The rest will come next PR. 6. Migrate much of the validation package `README.md` into the system package's main module `__init__.py` and migrate the examples into doctests. 7. Re-home a few other bits of functionality from validation to core. 8. Bring the https://github.com/vcschapp/overture-schema-pydantic scoping into core as `scoping.py` and fix up the linter errors. This is not wired up yet, but that's Coming Soon, likely in episode 4. 9. At Seth's suggestion, switch `ConfidenceScore` from `float64` to `float32` though we will have to double-check the actual value in the Parquet model here. Stay tuned for episode 3, where we will finish re-homing the validation package.

The destination is as described in PR #397 (1/N), PR #400, and PR #403. In this commit, the following value is added: 1. 🐞 Fix bug: The `not_required_if` mixin wasn't meeting the original schema intent, which result in the `DivisionBoundary` feature type having the wrong JSON Schema. The expected behavior is "if the boundary is at the country level, then the `country` pair should be omitted" but instead it did two variations: in the Python validator, it required the country pair to be present; and in the JSON Schema, it required the country pair to be present, but only if the condition was not true. Both were subtly wrong. The bug is fixed in this commit and the mixin is renamed to `forbid_if`, which I hope will make the semantics more obvious. 2. 🐞 Fix bug: Very subtle, but the mixin model constraint validators did not work correctly if added directly to a `Feature` model, because they aren't aware of the quirky multi-tiered GeoJSON JSON Schema where most properties get pushed down into "properties", but some do not. This is (hopefully ... 🤞) fixed in the new `Feature` model in the system package. 3. 🐞 Fix bug: Very subtle, but the previous `Feature` model's JSON Schema did not prohibit fields named `"id"`, `"bbox"`, and `"geometry"` within the properties object. This created a weird quirk where in a poisoned JSON object containing those values under properties, the properties version would overwrite the root version. This is fixed by explicitly prohibiting those fields in the JSON Schema for the `Feature` class' properties object. 4. 🐞 Fix bug: The `ExtensibleBaseModel`'s `patternProperties` got put both at the top level of the GeoJSON Feature schema and in the "properties" object schema. This would have allowed the input JSON to contain `ext_*` at two levels, which doesn't meet the original schema intent. As part of this bug fix, `ExtensibleBaseModel` is collapsed directly into `OvertureFeature` and the `ext_*` feature is documented as being on a deprecation path. 5. The `validation` package is officially deleted as its essential George functions have all been re-homed either into `system` or `core`. 6. All model constraint mixins have been refactored along the lines started in PR #400. They are now called `@forbid_if`, `@min_fields_set`, `@no_extra_fields`, `@radio_group`, `@require_any_of`, and `@require_if`. 7. A type hint, `Omitable[T]` has been added to the system package. This type hint allows a Pydantic model to "naturally" get JSON Schema semantics for omitted values - it de-conflates optionality and nullability, which Pydantic currently conflates. In an upcoming episode, I hope to replace the `X | None` unions in the existing model with `Omitable[X]`. 8. The existing `Feature` class from the `core` package has been split into two: (i) `Feature` in the `system` package now acts as a generic feature and owns all the funky GeoJSON logic, allowing George enthusiasts to work with a nice ergonomic feature type without having to use an "Overture"-flavored feature; (ii) `OvertureFeature` in the `core` package adds the Overture schema specific flavoring on top of `Feature`. 9. The `ref` module from `core` has been pushed down into `system` and the dependency on `(Overture)Feature` has been factored out in favor of a generic dependency on an `Identified` model, which is basically just a `BaseModel` with a mandatory ID. Stay tuned for episode 4, where we will re-organize the core package.

Victor Schappert (vcschapp) requested a review from Seth Fitzsimmons (sethfitz) October 3, 2025 00:17

Victor Schappert (vcschapp) temporarily deployed to staging October 3, 2025 00:17 — with GitHub Actions Inactive

Victor Schappert (vcschapp) temporarily deployed to staging October 3, 2025 00:19 — with GitHub Actions Inactive

Victor Schappert (vcschapp) commented Oct 3, 2025

View reviewed changes

Victor Schappert (vcschapp) added the change type - cosmetic 🌹 Cosmetic change label Oct 3, 2025

Seth Fitzsimmons (sethfitz) requested changes Oct 3, 2025

View reviewed changes

Seth Fitzsimmons (sethfitz) reviewed Oct 3, 2025

View reviewed changes

Comment thread Makefile Outdated

Victor Schappert (vcschapp) temporarily deployed to staging October 3, 2025 20:26 — with GitHub Actions Inactive

Victor Schappert (vcschapp) force-pushed the pydantic-packaging branch from a912f1a to 6bc4c71 Compare October 3, 2025 21:01

Victor Schappert (vcschapp) temporarily deployed to staging October 3, 2025 21:01 — with GitHub Actions Inactive

Victor Schappert (vcschapp) added 18 commits October 3, 2025 14:06

wip - repackage/modularize

4175250

wip - merge to pydantic main, making a huge mess along the way

4320c1f

This commit used to move "sources" out of the way for now, but that's over now after rebasing on Seth's #394.

wip - move bbox

c3dbf6f

wip - move primitive numeric types

0e2d001

wip - Document numeric primitives and add missing int16

16a1f4b

wip - replace LR base types with pct, but not done for Confidence yet

41ae7aa

wip - Migrate basic constraint, collection constraints

d2c4b5f

wip - Consistency: Rename WhitespaceConstraint -> StrippedConstraint …

d06c41e

…and TrimmedString -> StrippedString (stripped = Python term, not trim)

wip - Migrate string types/constraints out of validation package

dcb73d8

wip - Add TypeAlias to quiet Pylance warnings

b154fa0

wip - add unmodeled dependencies

76c617a

wip - Add pdoc and slightly modify foundation to make it pdoc friendly

ca9a048

wip - fix doctests and run them as part of make check

b8c14ac

add make target for docs format checking but don't make it mandatory …

3ef76af

…yet... ...Too many broken docs to bother

wip - CHECKS FAILING NOW - make mypy target work on parameterized pac…

53428d0

…kages

wip - Fix broken mypy checks in foundation package

5a74b04

wip - Rename 'foundation' package to 'system' to avoid OMF "Foundatio…

520f322

…n" overload

wip - Remove GERS stuff from diff

7da3ea4

Victor Schappert (vcschapp) added 2 commits October 3, 2025 14:16

wip - PR comment on 397 - fix sed pattern

66a6c65

#397 (comment) The proximate issue was that BSD `sed` on MacOS doesn't support alternation unless you use `-E`. But also the alternation wasn't needed, so I removed it.

wip - cherrypick back the changes from #394, eeeep

f202c57

Victor Schappert (vcschapp) force-pushed the pydantic-packaging branch from 6bc4c71 to f202c57 Compare October 3, 2025 21:21

Victor Schappert (vcschapp) temporarily deployed to staging October 3, 2025 21:21 — with GitHub Actions Inactive

Seth Fitzsimmons (sethfitz) approved these changes Oct 3, 2025

View reviewed changes

Seth Fitzsimmons (sethfitz) merged commit 7f88139 into pydantic Oct 3, 2025
4 checks passed

Seth Fitzsimmons (sethfitz) deleted the pydantic-packaging branch October 3, 2025 21:50

Victor Schappert (vcschapp) added a commit that referenced this pull request Oct 9, 2025

wip: Rename CountryCode -> CountryCodeAlpha2 as discussed on PR #397

3010719

#397

Victor Schappert (vcschapp) added a commit that referenced this pull request Oct 9, 2025

wip - Apply comment from PR #397 (pattern)

2cf4b9b

-#397 (comment)

Victor Schappert (vcschapp) mentioned this pull request Oct 9, 2025

Pydantic package organization episode 2: "The mess unfolds" #400

Merged

Victor Schappert (vcschapp) mentioned this pull request Oct 16, 2025

Pydantic package organization episode 3: "System update complete" #403

Merged

Victor Schappert (vcschapp) mentioned this pull request Oct 28, 2025

Pydantic package organization episode 4: "Scope is in (scope)" #412

Merged

Victor Schappert (vcschapp) mentioned this pull request Nov 5, 2025

Pydantic package organization episode 5: "Only mostly dead" #415

Merged

Victor Schappert (vcschapp) mentioned this pull request Mar 12, 2026

[REFACTOR] Organize divisions theme Pydantic package, add missing relationships, tidy and add docs #469

Merged

Victor Schappert (vcschapp) mentioned this pull request Jul 24, 2026

[REFACTOR] Organize transportation theme Pydantic package, add relationships, sync JSON Schema, and tidy docs #598

Merged

Victor Schappert (vcschapp) mentioned this pull request Jul 31, 2026

[REFACTOR] Delete annex, fix last docformat issues, enable docformat check in make check #629

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Pydantic package organization episode 1: "Making huge mess" - #397

Pydantic package organization episode 1: "Making huge mess"#397
Seth Fitzsimmons (sethfitz) merged 20 commits into
pydanticfrom
pydantic-packaging

Victor Schappert (vcschapp) commented Oct 3, 2025 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

Victor Schappert (vcschapp) commented Oct 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

tl;dr

Destination

Packaging Deep Dive

overture-schema-system

overture-schema-core

overture-schema-annex

overture-schema-***-theme

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Victor Schappert (vcschapp) commented Oct 3, 2025 •

edited

Loading