| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| Expand Up | @@ -126,3 +126,19 @@ export interface Config { | |
| */ | ||
| enableFileCoverageInformation: boolean; | ||
| } | ||
|
|
||
| /** Properties available in `Config`. */ | ||
| export type ActionConfigProperties = keyof Config; | ||
|
|
||
| /** | ||
| * The CodeQL Action configuration state that is persisted | ||
| * between steps of the CodeQL Action in a CodeQL workflow. | ||
| * | ||
| * By default, this is equivalent to `Config`. By explicitly | ||
| * providing required property names for `T` this can be restricted | ||
| * to requiring only those. For example, in `ActionConfig<"codeqlCmd">` | ||
| * all properties except `codeqlCmd` are optional. | ||
| */ | ||
| export type ActionConfig< | ||
|
Comment thread
Copy link
Copy Markdown
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low QualityBikeshed: ConfigWith? Also, we should be careful with properties that might be optional, e.g. buildMode can be undefined in a successful configuration.
Sorry, something went wrong.
All reactions
Copy link
Copy Markdown
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low QualitySome time ago we talked about how Config is an awful name for the type and that it's really more representing the state of the Action that we persist across steps. It's also ambiguous as to whether it refers to the Action, CLI, or something else. I thought that I would use this opportunity to move away from that and introduce a better name.
Sorry, something went wrong.
All reactions
Copy link
Copy Markdown
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low QualityMy one comment about ActionConfig is that it's quite easy to confuse with ActionState, e.g. you mention "A new ActionState type is added" in the PR description. But I agree it's good to clarify that we're talking about Action configuration.
Sorry, something went wrong.
mbg reacted with thumbs up emoji
All reactions
Copy link
Copy Markdown
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low QualityGood point and I have fixed that in the PR description now. I can't really think of a better name right now, but open to suggestions (and happy to rename as a follow-up).
Sorry, something went wrong.
All reactions
|
||
| T extends ActionConfigProperties = ActionConfigProperties, | ||
| > = Partial<Config> & Pick<Config, T>; | ||
| Back | FazBrowse Home | New Git URL |
Uh oh!
There was an error while loading. Please reload this page.