Conversation
|
@logonoff: This pull request references Jira Issue OCPBUGS-65887, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@logonoff: This pull request references Jira Issue OCPBUGS-65887, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@logonoff: This pull request references Jira Issue OCPBUGS-65887, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
bb3f145 to
6c4adfd
Compare
6c4adfd to
7016f3b
Compare
| @@ -1,5 +1,10 @@ | |||
| { | |||
| "typescript.tsdk": "./node_modules/typescript/lib", | |||
| "editor.formatOnSave": false, | |||
There was a problem hiding this comment.
Do we need this to be an explicit option?
Does setting editor.codeActionsOnSave cause editor.formatOnSave to be enabled by default?
There was a problem hiding this comment.
We should explicitly disable formatOnSave (even overriding user workspace preferences) because it has problems with our eslint config. codeActionsOnSave is run before formatOnSave, but the formatOnSave formatting is incorrect according to the linter. This is very annoying.
| with this namespace as follows: | ||
|
|
||
| ```tsx | ||
| conster Header: React.FC = () => { |
There was a problem hiding this comment.
😆 conster sounds like a const but stronger
package.json
Outdated
| "@babel/preset-env": "^7.28.5", | ||
| "@cypress/webpack-preprocessor": "^7.0.2", | ||
| "@openshift-console/dynamic-plugin-sdk": "4.19.1", | ||
| "@openshift-console/dynamic-plugin-sdk-webpack": "4.19.0", |
There was a problem hiding this comment.
Big update to Console plugin SDK packages 👍
| }, | ||
| "dependencies": { | ||
| "@console/pluginAPI": "*" | ||
| "@console/pluginAPI": "^4.19.0" |
There was a problem hiding this comment.
This should encourage real world plugins to utilize the @console/pluginAPI dependency 👍
| "jsx": "react-jsx", | ||
| "allowJs": true, | ||
| "strict": false, | ||
| "strict": true, |
There was a problem hiding this comment.
👍 for the switch to TS strict mode
9631b59 to
ec19900
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: logonoff The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
af8a1c4 to
6075b34
Compare
|
/retest |
2 similar comments
|
/retest |
|
/retest |
|
@logonoff: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |

Closes #92
after: