-
Notifications
You must be signed in to change notification settings - Fork 527
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
feat: add the service page upstream select option #1633
feat: add the service page upstream select option #1633
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1633 +/- ##
===========================================
- Coverage 72.08% 52.29% -19.80%
===========================================
Files 130 38 -92
Lines 5649 2660 -2989
Branches 648 0 -648
===========================================
- Hits 4072 1391 -2681
+ Misses 1333 1081 -252
+ Partials 244 188 -56
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
cc @guoqqqi to check the e2e. |
may sync the master branch |
…pisix-dashboard into fix-#1616-add-upstream-option
Done 😀 |
Hi @liuxiran Thanks for your detailed explanation, I update the commit please review it again. |
web/cypress/integration/route/can-skip-upstream-when-select-service-id.spec.js
Outdated
Show resolved
Hide resolved
web/cypress/integration/route/can-skip-upstream-when-select-service-id.spec.js
Outdated
Show resolved
Hide resolved
Hi, @stu01509 I noticed that when editing the service, the upstream information that was customized at creation disappeared, which I think should be visible here. |
Hi @guoqqqi Update the commit, I change the LINE#92 cy.contains('None').should('be.visible'); |
No, What I mean is that the data upstream of the creation of the service is now lost when editing. |
Hi @stu01509 , you have to deal with the confilct first, thanks Judging from the error log, when creating a service, cypress try to find dom so it would be better to set the default upstream selection to |
…pisix-dashboard into fix-#1616-add-upstream-option
Hi @juzhiyuan @liuxiran @nic-chen, and @guoqqqi I update the commit, and fix the ci error, please review it again, thanks. |
hi @stu01509 |
@stu01509 Hi, I just noticed this PR, once this conflicts get resolved, I will continue reviewing it. |
Ok, I will solve it later. |
Deploy preview for apisix-dashboard ready! Built with commit cfe100c |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1633 +/- ##
==========================================
+ Coverage 72.07% 72.13% +0.05%
==========================================
Files 125 125
Lines 2944 2943 -1
Branches 711 710 -1
==========================================
+ Hits 2122 2123 +1
+ Misses 822 820 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Hi @stu01509, after fix this problem, please continue to fix can not submit data in the last step of creating service when select upstream None
hope this commit can help you: liuxiran@d75b137
thanks
Please answer these questions before submitting a pull request
Why submit this pull request?
Bugfix
New feature provided
Improve performance
Backport patches
Related issues
Fix when creating a
Service
,Select Upstream
should be optional, not required #1616New feature or improvement
Add the None option in the service page upstream select.