feat: add per-category blocked roles-list#495
feat: add per-category blocked roles-list#495itzwam wants to merge 1 commit intodiscord-tickets:mainfrom
Conversation
|
@itzwam how would you use this feature? |
|
Late reply cuz I didn't see your message, on my side there are some ticketing categories that are allowed for all roles let's say I create 12 roles on my server, I dont want to update the allowed-list with every-roles-but-one, instead I'prefer to specify a blocked role and it works perfectly that's a workflow I already use locally and I would like to upstream this change to the bot cuz I don't think I'm the only one who needs it |
|
Just figured-out the DB migrations I edited aren't the good ones, think I will need to create new schema migrations files for this specific upgrade, but not sure how to do it properly it "worked" like that but pretty sure I'm not supposed to edit old schema migration scripts. |
eartharoid
left a comment
There was a problem hiding this comment.
Yes, the SQL files should be reverted.
The process for generating new migrations is to use primsa migrate dev for each of the providers.
|
we need to apply change on files and restarting bot or a bit complicated for apply this change? thx |
~ db/postgresql/schema.prisma: ~ db/sqlite/schema.prisma: ~ src/lib/middleware/prisma-sqlite.js: ~ src/lib/tickets/manager.js: ~ src/routes/api/admin/guilds/[guild]/categories/[category]/index.js: ~ src/routes/api/admin/guilds/[guild]/categories/index.js:
|
Removed schema migrations + squashed things will try to run primsa migrate dev on my side |
eartharoid
left a comment
There was a problem hiding this comment.
Thank you, this looks perfect. I'll merge it into a v4.1 branch when I have other schema changes so I can add them in a single db migration.
|
Hi are there any news on this ❤️ I've been looking to block some roles in our system and would've pr'ed it myself, but found this pr rn |
Versioning information
Is this related to an issue?
Changes made
Added per-category roles blocklist
Confirmations