Repository navigation
Conversation
4 tasks done
This branch has not been deployed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Follow-up to apache/shenyu#7677 (apache/shenyu#7589). The Admin API renames the request field to
logged(the oldlogedis accepted for one release via@JsonAlias), and responses now always serializelogged.This updates the form field name and the related object properties in
Selector.js,Rule.js, andToolsModal.js(18 occurrences) so the console keeps working against the renamed contract.Without this change, the next dashboard rebuild would regenerate the checked-in bundle in apache/shenyu from the old field name and silently revert the rename in apache/shenyu#7677.
Checklist