-
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
chore: refactor upstream form module #1726
chore: refactor upstream form module #1726
Conversation
chore: improve Route module (apache#1715)
Hi, I noticed that there have too many changes! This is due to I separate the UpstreamForm file (more than 813 lines) into some sub-components, to make this module more clear for developers. According to the schema_def file: https://github.com/apache/apisix/blob/master/apisix/schema_def.lua#L114 , I structured the components according to fields style. e.g |
This PR doesn't change logics, only adjust the structure so we could know more clear about this component. Test is under debugging. |
fix: When editing a route, the "URI override" radio button‘s value is…
Codecov Report
@@ Coverage Diff @@
## master #1726 +/- ##
==========================================
- Coverage 71.86% 71.61% -0.26%
==========================================
Files 47 47
Lines 3128 3128
==========================================
- Hits 2248 2240 -8
- Misses 638 645 +7
- Partials 242 243 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
@juzhiyuan the adjustment is OK on my side which makes the code structure much more intuitive and easier for maintenance. |
yes! And if we want to use the field like BTW, backend CI failed due to |
I'm honored to have this Component got structure updated :) |
retries: 1 | ||
type: 'roundrobin', | ||
checks: {}, | ||
scheme: "http", |
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 keep same style ""
or ' '
.
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, will be formatted globally in a new PR.
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.
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
Thanks, @juzhiyuan.
Hi @liuxiran, this PR needs your review :) You could review this one first, after issues you find (maybe) are resolved, I will add features for Upstream. |
Please answer these questions before submitting a pull request, or your PR will get closed.
Why submit this pull request?
What changes will this PR take into?
Checklist: