-
Notifications
You must be signed in to change notification settings - Fork 667
Add console-scripts package #1411
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
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: vojtechszocs If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@vojtechszocs: GitHub didn't allow me to request PR reviews from the following users: mareklibra, rawagner, jelkosz. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. 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 kubernetes/test-infra repository. |
Edit: forgot to switch to |
| @@ -0,0 +1,5 @@ | |||
| { | |||
| "extends": [ | |||
| "../../integration-tests/.eslintrc" | |||
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.
Normally I'd create named ESLint configs, e.g. .eslintrc.node and .eslintrc.browser, but wanted to minimize my changes so just reusing an existing one for now.
|
/retest |
|
@vojtechszocs often we add an argument to run a specific test, or extra jest options. Looks like this will not work with this approach when running the |
That's a good point, I missed that 😐 I'll update the |
|
I don't think you can simply pass all the args because you're also adding the dir as an arg to run tests for the package. If the user wants to run tests for a specific file, they can't do so as all tests in the package will still be picked up. |
|
@vojtechszocs: PR needs rebase. 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/test-infra repository. |
|
/hold |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
|
@vojtechszocs: 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/test-infra repository. I understand the commands that are listed here. |
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
|
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
|
@openshift-bot: Closed this PR. 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 kubernetes/test-infra repository. |
This PR adds new
console-scriptspackage containing common scripts available to all packages.This is conceptually similar to fabric8-ui
scriptspackage. Reusing scripts across packages allows for aligning common workflows such as testing, linting, etc. and therefore improve monorepo cohesiveness."scripts": { - "test": "yarn --cwd ../.. run test packages/console-shared" + "test": "console-test" }Here's what happens when you run the
console-testscript:yarn test packages/<caller-pkg>in the monorepo root directoryNote: Jest
testRegexoption was modified to allow future test co-location.I've tested this by adding a temporary
packages/console-shared/src/index.test.jsfile and runningyarn testin the monorepo root and then in thepackages/console-shareddirectory. Both global and package-specifictestworkflow works as expected.