Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Old pseudo-versioned plans need to be migrated to new system

Open
#108 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
backend, database

Research direction

Start by locating the persistence code for plans and plan_version, then trace how plans are associated with an agreement and how canonical_id is stored. Define the one-off migration around the existing records described in the issue; it is done when related plans share the intended canonical_id and the required plan_version rows exist after a safe production run.

Written by the indexing model from the issue text.

Description

The previous "versioning" that was done created multiple plans for an agreement. These records should be updated to all have the same canonical_id value (most likely set to the id of the latest plan), and related plan_version rows created. Preferably, this will be some kind of script that we will run once after merging the versioning changes into prod.

Dominant language
TypeScript
Stars
1
Forks
7
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bcgov/range-api

All issues in bcgov/range-api

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.