feat: integrate geometry repair pipeline across services + docs & integration tests - #80
Open
dhimashary wants to merge 29 commits into
Open
feat: integrate geometry repair pipeline across services + docs & integration tests#80dhimashary wants to merge 29 commits into
dhimashary wants to merge 29 commits into
Conversation
… and simulation-backend
…r integration testing
… and simulation-backend
# Conflicts: # backend # docker-compose.test.yml # frontend-v2 # simulation-backend
Documentation build overview
14 files changed ·
|
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.
Geometry Repair Pipeline – Integration
Wires the geometry inspection & repair feature together across all services,
adds the geometry-pipeline as a submodule.
Submodules
geometry-pipelineas a new submodule.backend,frontend-v2, andsimulation-backendpointers to thecommits containing the repair-pipeline work.
Integration test stack
docker-compose.test.yml: a self-contained stack for running the backendgeometry-pipeline integration tests against real Docker.
db-testPostgres (choras_test, host port5433, tmpfs) so itnever touches the dev database.
backend-testbuilds from the repo root, bind-mountssimulation-backendand
tests/for fast iteration, and runspytest tests/geometry_pipeline_integrationinstead of the app entrypoint..env.testwith the isolated test configuration.Documentation
docs/source/includes/ geometry_validation/, with one page per issue type: duplicate vertices,zero-area faces, non-planar faces, T-junctions, self-intersections, boundary
edges, possible holes, small faces, collinear faces, overlapping faces.
index.rstand the contribute-a-method guide.Reviewer notes
.gitmodulescurrently points several submodules topersonal forks (
dhimashary/*) and feature branches. These should berepointed to the
choras-orgrepos / merged commits once the component PRs(backend
feat/geometry-repair-pipeline, frontendfeat/repair-page,simulation-backend
geometry-pipeline-integration) are merged.