[ACA-4695] Fix saving screenshots for E2Es, add nx eslint plugin #3148
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MichalKinas
requested review from
TomikaArome,
nikita-web-ua and
AleksanderSklorz
AleksanderSklorz
approved these changes
Apr 25, 2023
DenysVuika
approved these changes
Apr 25, 2023
nikita-web-ua
approved these changes
Apr 26, 2023
MichalKinas
deleted the
feature/dev-mkinas-ACA-4695-fix-saving-failing-e-2-es-screenshots
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behaviour? (You can also link to an open issue here)
Failing E2Es sreenshots are not being saved.
What is the new behaviour?
Screenshots are now uploaded and can be accessed. Also nx eslint plugin has been added to correctly lint .js files. https://alfresco.atlassian.net/browse/ACA-4695
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: