-
Notifications
You must be signed in to change notification settings - Fork 5
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
Project Workflow - PMs should not be able to bypass Consultant checks for Internships #3231
Conversation
This means that a single transition can have multiple states based on other things (like project state).
This opens the door for `from` field & generic abstraction
Disallow direct access to member values when referencing generically ```ts let Color: MadeEnum<'red' | 'blue'>; let AnEnum: MadeEnum<string>; ``` Without this change `Color` can't be assigned to `AnEnum`, because the TS defines the member values as an index: `{ [x: string]: string }`. So since one has an index accessor and one doesn't, making them incompatible. The `entry()` arg type change also allows them to be compatible. Without it TS thinks something like `entry()` fn accepting any `string` is not compatible with `entry()` fn only accepting `'red' | 'blue'`. Using another generic at the function level somehow works around this, while still maintaining all the strictness.
@@ -23,6 +24,45 @@ export const IsMultiplication: Condition = { | |||
}, | |||
}; | |||
|
|||
export const hasValidRoleForProjectType: Condition = { |
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.
This is an authorization concern, so the policies should handle it. We need to just figure out how to get the "internship type condition" there. Let me think about it.
I get that it's kinda weird since we have two ways and both have conditions.
84af753
to
b2e86fa
Compare
This was actually implemented in 55777cd |
Monday