-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
♻️ rename tag label to subject #344
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Je pense qu'en toute logique on devrait aussi renommer le type TagCategory
en SubjectCategory
.
e9bbb48
to
940a481
Compare
specialists: [User!]! @relation(name: "UserSpecialties", link: TABLE) | ||
|
||
order: Int! | ||
category: TagCategory! @relation(name: "TagLabelsCategory", link: TABLE) | ||
category: SubjectCategory! @relation(name: "TagLabelsCategory", link: TABLE) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Le nom de la relation doit changer aussi, pour être cohérent
@@ -166,7 +166,7 @@ type Configuration { | |||
slackCommandKey: String | |||
|
|||
tags: Json | |||
tagCategories: [TagCategory!]! @relation(name: "ConfigurationTags", onDelete: CASCADE) | |||
subjectCategories: [SubjectCategory!]! @relation(name: "ConfigurationTags", onDelete: CASCADE) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Le nom de la relation doit changer aussi, pour être cohérent
No description provided.