Pil0tXia opened a new pull request, #4524:
URL: https://github.com/apache/eventmesh/pull/4524

   <!--
   ### 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 #4521.
   
   ### Motivation
   
   The Message subclass represents the string message for exceptions; however, 
its concept may potentially conflict with MQ messages. To address this concern, 
the class name has been changed while retaining the field name.
   
   Type refers to a kind or category, where its constituents share similar 
characteristics. It can pertain to a single exception or multiple exceptions of 
the same type, which might lead to potential ambiguity. Therefore, its class 
name has been exacted to the primary classification level `Category`.
   
   ### Modifications
   
   The names of various exception enumeration classes have been optimized to 
better align with their usage in the code, adhere more closely to English 
grammar, and avoid potential conflicts with future-introduced concepts.
   
   ### Documentation
   
   - Does this pull request introduce a new feature? (yes / no)
   - If yes, how is the feature documented? (not applicable / docs / JavaDocs / 
not documented)
   - 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]

Reply via email to