rainbownapkin/canopy
1
0
Fork 0
Code Issues 2 Pull requests Actions Packages Projects Releases Wiki Activity

Dynamically generate permissionsMap and channelPemissionsMap validation schemas in permissionsValidator.js #60

New issue
Closed
opened 2024-12-11 06:16:35 -05:00 by rainbownapkin · 1 comment
rainbownapkin commented 2024-12-11 06:16:35 -05:00 (Migrated from gitlab.com)
Copy link

Currently when adding new permissions to canopy there are two steps:

  • Add the permission to the permissions/channelPermissions DB Schema
  • Add the permission to the permissions/channelPermissions validation schema

If we checked the DB and dynamically filled the validation schema on startup it would only take a change of one file in one place to add new permission types to canopy

Currently when adding new permissions to canopy there are two steps: - Add the permission to the permissions/channelPermissions DB Schema - Add the permission to the permissions/channelPermissions validation schema If we checked the DB and dynamically filled the validation schema on startup it would only take a change of one file in one place to add new permission types to canopy
rainbownapkin commented 2024-12-15 19:07:05 -05:00 (Migrated from gitlab.com)
Copy link

Permissions validation schemas now dynamically generate from database schemas: 1bf89e62e7

Permissions validation schemas now dynamically generate from database schemas: 1bf89e62e796979a0c0b6e40b46aece388356d32
rainbownapkin (Migrated from gitlab.com) closed this issue 2024-12-15 19:07:06 -05:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
dev
0.4-indev-hotfix-3
0.4-indev-hotfix-2
0.4-indev-hotfix-1
0.4-indev
0.3-indev-hotfix-1
0.3-indev
verbose-queue
0.2-indev
0.1-indev
No results found.
Labels
Clear labels   
Bug

   
Cleanup/Refactor

   
Core Feature

   
Documentation

   
Feature

   
Performance Improvement

   
Security Improvement

   
UX/Accessibility

   
Unreproducable Bug
No labels
Bug
Cleanup/Refactor
Core Feature
Documentation
Feature
Performance Improvement
Security Improvement
UX/Accessibility
Unreproducable Bug
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: rainbownapkin/canopy#60
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?