Remove Vue set for vue 3 migration
What does this MR do and why?
Describe in detail what your merge request does and why.
This MR partially resolves #452467 (closed)
What was cleaned up from epic:
- Remove
Vue.set
Vue set is no longer supported in VUE 3
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
NO VISUAL CHANGES
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
- Checkout branch
- Run test locally
- Or just check in pipeline
- Run it also with
VUE_VERSION=3 yarn jest --watch
You can check via UI
- Go to project
- Releases
- Add several milestones (create one if does not exist)
- Clear milestones
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Merge request reports
Activity
assigned to @arfedoro
2 Warnings This merge request does not refer to an existing milestone. You've made some app changes, but didn't add any tests.
That's OK as long as you're refactoring existing code,
but please consider adding any of the maintenancepipelines, maintenancerefactor, maintenanceworkflow, documentation, QA labels.1 Message CHANGELOG missing: If this merge request needs a changelog entry, add the
Changelog
trailer to the commit message you want to add to the changelog.If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.
Reviewer roulette
Category Reviewer Maintainer frontend @robyrne
(UTC+2, same timezone as author)
@ohoral
(UTC+3, 1 hour ahead of author)
Please check reviewer's status!
Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger- Resolved by Olena Horal-Koretska
@arfedoro - please see the following guidance and update this merge request.1 Error Please add typebug typefeature, or typemaintenance label to this merge request.
Bundle size analysis [beta]
This compares changes in bundle size for entry points between the commits f8f15106 and 31a8404e
Special assetsEntrypoint / Name Size before Size after Diff Diff in percent average 4.31 MB 4.31 MB - -0.0 % mainChunk 3.3 MB 3.3 MB - 0.0 %
Note: We do not have exact data for f8f15106. So we have used data from: 37132b16.
The target commit was too new, so we used the latest commit from master we have info on.
It might help to rerun thebundle-size-review
job
This might mean that you have a few false positives in this report. If something unrelated to your code changes is reported, you can check this comparison in order to see if they caused this change.Please look at the full report for more details
Read more about how this report works.
Generated by
Danger- Resolved by Artur Fedorov
@dstull could you please review this?
requested review from @dstull
added pipeline:mr-approved label
- Resolved by Artur Fedorov
@dstull
, thanks for approving this merge request.This is the first time the merge request has been approved. To ensure we don't only run predictive pipelines, and we don't break
master
, a new pipeline will be started shortly.Please wait for the pipeline to start before resolving this discussion and set auto-merge for the new pipeline. See merging a merge request for more details.
@arfedoro Some end-to-end (E2E) tests should run based on the stage label.
Please start the
manual:e2e-test-pipeline-generate
job in theprepare
stage and wait for the tests in thefollow-up:e2e:package-and-test-ee
pipeline to pass before merging this MR. Do not use Auto-merge, unless these tests have already completed successfully, because a failure in these tests do not block the auto-merge. (E2E tests are computationally intensive and don't run automatically for every push/rebase, so we ask you to run this job manually at least once.)To run all E2E tests, apply the pipeline:run-all-e2e label and run a new pipeline.
E2E test jobs are allowed to fail due to flakiness. See current failures at the latest pipeline triage issue.
Once done, apply the
emoji on this comment.Team members only: for any questions or help, reach out on the internal
#test-platform
Slack channel.E2E Test Result Summary
allure-report-publisher
generated test report!e2e-test-on-gdk:
test report for 31a8404eexpand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Package | 18 | 0 | 12 | 0 | 30 | ✅ | | Govern | 66 | 0 | 0 | 0 | 66 | ✅ | | Verify | 28 | 0 | 1 | 0 | 29 | ✅ | | Plan | 44 | 0 | 0 | 0 | 44 | ✅ | | Create | 93 | 0 | 8 | 0 | 101 | ✅ | | Data Stores | 25 | 0 | 4 | 0 | 29 | ✅ | | Monitor | 7 | 0 | 0 | 0 | 7 | ✅ | | Manage | 0 | 0 | 1 | 0 | 1 | ➖ | | Release | 5 | 0 | 0 | 0 | 5 | ✅ | | Analytics | 1 | 0 | 0 | 0 | 1 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 287 | 0 | 26 | 0 | 313 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
enabled an automatic merge when all merge checks for 31a8404e pass
added typemaintenance label
mentioned in commit 25e78936
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
changed milestone to %17.0
added workflowpost-deploy-db-staging label and removed workflowproduction label
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label
added pipelinetier-3 label