bcgov / bcgov/range-web

INFO - Amendments General

Open
#708 0 comments 0 reactions 1 assignee Claimed by @LisaMoore1 View on GitHub
Dominant language
TypeScript
Stars
9
Forks
11
PR merge metrics
No merged PRs in 30d

Description

These are for thought — I’m open to discussion but each touches on an important principle that needs to be addressed (see #703) for other relevant info. This one is mostly covered in duplicate for minor/mandatory amendment specific ones but I haven’t double checked yet and don’t want to lose these ideas.

- [ ] headers need to be relevant to amendments
- either generic enough to match whether original or amendments OR specific ones for when something is an amendment in progress
- if the non-initiating user type can see there is a version but they can’t open it they need messaging to indicate why or they will think something is broken
- [ ] the amendment version needs to be clearly labelled “In Progress Amendment”
- [ ] amendments can only be built off of “current legal” versions not anything else

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.