[INTW26] Add isArchived to positions and isActive to users #114
Conversation
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
Add archived/active flags to positions and users with defaults via migration
Apply Prettier formatting so lint passes for the new migration
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.
Notion ticket link
Update Positions and Users Table to Support Archived Positions
Implementation description
positions.isArchived(boolean, NOT NULL, defaultfalse) via migration and Sequelize model.users.isActive(boolean, NOT NULL, defaulttrue) via migration and Sequelize model.Steps to test
docker exec recruitment_tools_backend node migrate up.positionshasisArchived boolean not null default false(e.g.\d positions).usershasisActive boolean not null default true(e.g.\d users).What should reviewers focus on?