-
Notifications
You must be signed in to change notification settings - Fork 120
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
RELATED: FET-769 Migrate to pure ESM #3802
Conversation
Merge Failed. Zuul merger could not merge this change into the base branch. This is most likely caused by merge conflicts. Please rebase the change and upload the rebased version. In case of further errors, contact the zuul administrator. |
2 similar comments
Merge Failed. Zuul merger could not merge this change into the base branch. This is most likely caused by merge conflicts. Please rebase the change and upload the rebased version. In case of further errors, contact the zuul administrator. |
Merge Failed. Zuul merger could not merge this change into the base branch. This is most likely caused by merge conflicts. Please rebase the change and upload the rebased version. In case of further errors, contact the zuul administrator. |
c00950d
to
0017316
Compare
Merge Failed. Zuul merger could not merge this change into the base branch. This is most likely caused by merge conflicts. Please rebase the change and upload the rebased version. In case of further errors, contact the zuul administrator. |
18d50f8
to
eb47f9a
Compare
Build in pipeline check aborted. |
Build failed (check pipeline). |
eb47f9a
to
9582af1
Compare
Build failed (check pipeline). |
9582af1
to
33adae6
Compare
Build failed (check pipeline). |
33adae6
to
b6b20dd
Compare
Build failed (check pipeline). |
b6b20dd
to
4dfac3a
Compare
Build failed (check pipeline). |
4dfac3a
to
2e9a164
Compare
Build failed (check pipeline). |
Build failed (check pipeline). |
Build failed (check pipeline). |
Build failed (check pipeline). |
c57c0b0
to
3771c01
Compare
Build failed (check pipeline). |
3771c01
to
9348508
Compare
Build failed (check pipeline). |
9348508
to
da0123d
Compare
Build failed (check pipeline). |
Merge Failed. Zuul merger could not merge this change into the base branch. This is most likely caused by merge conflicts. Please rebase the change and upload the rebased version. In case of further errors, contact the zuul administrator. |
Build failed (check-extended pipeline). |
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.
LGTM
common/scripts/directory.mjs
Outdated
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.
We should remove this file with hardcoded path.
If we want to keep the script with extensions fix, we should make it parametrized, but I think we can remove it as well.
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.
done
common/scripts/fix-ext.mjs
Outdated
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.
Should we remove this script? Or at least, make it parametrized?
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.
done
common/scripts/fix-invariant.mjs
Outdated
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.
Should we remove this script? Or at least, make it parametrized?
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.
done
common/scripts/fix-lodash.mjs
Outdated
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.
Should we remove this script? Or at least, make it parametrized?
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.
done
docs/contributing.md
Outdated
@@ -45,7 +45,7 @@ Always run `rush install`; this will make sure all the dependencies from the loc | |||
the projects managed in the repository. After that run `rush build`. | |||
|
|||
In case the pull brings in new projects or large bulk of changes, it is safer (albeit more time-consuming) to run | |||
`rush install && rush link --force && rush clean && rush rebuild`. | |||
`rush purge rush install && rush rebuild`. |
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.
Should it be rush clean && rush purge && rush install && rush rebuild
?
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.
done
"plugin:sonarjs/recommended", | ||
"plugin:regexp/recommended", | ||
"plugin:react-hooks/recommended", | ||
"../../.eslintrc.react.js", |
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.
Why this removal (of react eslint extend)?
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.
added back
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.
Can we use .js or .mjs for the webpack config?
@@ -106,24 +106,39 @@ module.exports = async (env, argv) => { | |||
entry: ["./src/index.tsx"], | |||
target: "web", | |||
mode: isProduction ? "production" : "development", | |||
experiments: { | |||
outputModule: true, |
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.
Should we use this, as it's still experimental?
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.
we have no other option
publicPath: `${basePath}/`, | ||
library: { | ||
type: "module", |
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.
Technically, playground is not a library, does this really need to be there?
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.
Yes its necessary
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.
Again, is it feasible to migrate this config to esm? (we can handle it as a followup)
Build in pipeline check aborted. |
Sonar scan resultMore detail, see in https://sonarqube-gate.intgdc.com/dashboard?id=gooddata-ui-sdk-gate-PR3802 To scan for vulnerabilities in dependencies and run unit tests (to get coverage report in sonar) please comment your PR with 'extended check sonar'. |
Build failed (gate pipeline).
|
extended test - matrix-test |
Build failed (check-extended pipeline). |
extended test - matrix-test |
Build failed (check-extended pipeline). |
Build succeeded (check pipeline). |
764ac4c
to
b463f58
Compare
extended test - matrix-test |
Build failed (check-extended pipeline). |
extended test - matrix-test |
Build succeeded (check pipeline). |
Build succeeded (check-extended pipeline). |
b463f58
to
5e323cd
Compare
JIRA: FET-769
5e323cd
to
d34af6f
Compare
Build in pipeline check aborted. |
Build succeeded (check pipeline). |
Sonar scan resultMore detail, see in https://sonarqube-gate.intgdc.com/dashboard?id=gooddata-ui-sdk-gate-PR3802 To scan for vulnerabilities in dependencies and run unit tests (to get coverage report in sonar) please comment your PR with 'extended check sonar'. |
Build succeeded (gate pipeline).
|
Supported PR commands:
ok to test
extended check sonar
extended test - backstop
extended test - tiger-cypress - isolated <testName>
extended test - tiger-cypress - record <testName>
extended test - tiger-cypress - integrated <testName>
extended test - cypress - isolated <testName>
extended test - cypress - record <testName>
extended test - cypress - integrated <testName>
extended test - matrix-test <AIO_version>
<testName>
in cypress commands is used to filter specfiles. Example, to run record with BEAR backenddashboard.spec.ts
anddrilling.spec.ts
, execute commandextended test - cypress - record dashboard,drilling
extended test - cypress - record
orextended test - cypress - record *
<AIO_version>
in commands is used to start test with multiple AIO instances - each instance in triggered by one jenkins buildmaster
andstable
, execute commandextended test - matrix-test master,stable
orextended test - matrix-test latest
2.3.0
and2.3.1
, execute commandextended test - matrix-test 2.3.0,2.3.1
<AIO_version>
is empty, read versions from filecompTigerVersions.txt
of this repoPR Checklist
check
passesextended test - backstop
passesextended test - tiger-cypress - record
to record new mapping files (Tiger BE)extended test - cypress - record
to record new mapping files (Bear BE)extended test - tiger-cypress - isolated
passesextended test - cypress - isolated
passesextended test - tiger-cypress - integrated
passesrush change
was run if applicable