Pil0tXia opened a new pull request, #4813:
URL: https://github.com/apache/eventmesh/pull/4813
<!--
### Contribution Checklist
- Name the pull request in the form "[ISSUE #XXXX] Title of the pull
request",
where *XXXX* should be replaced by the actual issue number.
Skip *[ISSUE #XXXX]* if there is no associated github issue for this
pull request.
- Fill out the template below to describe the changes contributed by the
pull request.
That will give reviewers the context they need to do the review.
- Each pull request should address only one issue.
Please do not mix up code from multiple issues.
- Each commit in the pull request should have a meaningful commit message.
- Once all items of the checklist are addressed, remove the above text and
this checklist,
leaving only the filled out template below.
(The sections below can be removed for hotfixes of typos)
-->
<!--
(If this PR fixes a GitHub issue, please add `Fixes #<XXX>` or `Closes
#<XXX>`.)
-->
Fixes #4812
### Motivation
Organize and optimize the code merged in
https://github.com/apache/eventmesh/pull/4768, and implement v2 endpoints used
for the new EventMesh Dashboard.
### Modifications
- Added PUT method to
`org.apache.eventmesh.runtime.admin.handler.AbstractHttpHandler#handle`
- Eliminated the step of `getBytes` in
`org.apache.eventmesh.runtime.admin.handler.AbstractHttpHandler#write`
- No need to construct `HttpResponse` with cross-origin headers in endpoint
implementation code
- Cleaned up various overloaded methods that were messy and non-hierarchical
- For old endpoints, the path remains unchanged temporarily (endpoint path
needs modification by Next.js Dashboard), suffix class names with V1, moved to
v1 package; for new endpoints, use path /v2, do not suffix class names with V2,
placed in v2 package.
- Corrected incorrect naming of annotations such as `@ConfigField`
- Implemented `/v2/configuration` endpoint, returning all Runtime
configurations.
For detailed changes, refer to the naming of each commit.
### Documentation
- Does this pull request introduce a new feature? (yes)
- If yes, how is the feature documented? (JavaDocs)
- If a feature is not applicable for documentation, explain why?
- If a feature is not documented yet in this PR, please create a followup
issue for adding the documentation
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
