Add ITRS-classification support for cycling routes#168
Open
Add ITRS-classification support for cycling routes#168
Conversation
vharmain
force-pushed
the
feature/itrs-classification
branch
3 times, most recently
from
ecb892f to
2b867ef
Compare
vharmain
force-pushed
the
feature/itrs-classification
branch
from
2b867ef to
65d7765
Compare
vharmain
force-pushed
the
feature/itrs-classification
branch
2 times, most recently
from
8de2f7a to
830d6cb
Compare
vharmain
force-pushed
the
feature/itrs-classification
branch
from
830d6cb to
8eb5428
Compare
vharmain
force-pushed
the
feature/itrs-classification
branch
from
8eb5428 to
b5ee5ca
Compare
vharmain
force-pushed
the
feature/itrs-classification
branch
2 times, most recently
from
b1f64b9 to
78e0d44
Compare
vharmain
force-pushed
the
feature/itrs-classification
branch
from
5ec1b1c to
d62a4bf
Compare
Post-merge fix: this component came from feature/itrs-classification and still used defui/$, which broke the production build after merging the UIX removal branch. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
ITRS fields (route-level and segment-level) are now gated by a dedicated :itrs/edit privilege instead of reusing :activity/edit. This allows ITRS editing to be controlled independently via the new :itrs-assessor role. Disabled ITRS fields show a tooltip explaining the required role. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
… reload The namespace contains a macro that reads translations from .edn files. Without ^:dev/always, shadow-cljs skips reloading it and translation changes don't take effect until a full recompile. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The single-route branch in the ::routes condp was commented out with #_#_, so persisted routes with one entry had no :fids. This caused compute-itrs-technical to match zero features and always return nil. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…assification - Remove itrs-exposure from segment feature properties and UI - Add "trail-conditions" LOI category with fall-hazard type carrying ITRS exposure (E1-E4) - Add :itrs-technical-route field to route properties with auto-compute button that calculates max technical value from route segments - Add i18n translations for compute-itrs-technical in fi/en/se Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…der feedback Rename endurance/wilderness/technical fields, fix "vaikea" → "vaativa" in technical options, replace E-prefixed exposure labels with consequence-based texts, and migrate remaining legacy mui/ refs to explicit MUI imports. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
vharmain
force-pushed
the
feature/itrs-classification
branch
from
3a93104 to
999d294
Compare
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.
See webapp/docs/itrs.md