Refactor team leader name handling in MGX environment #1907
+3
−2
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.
This pull request updates the handling of the team leader's name within the
MGXEnvclass to make it configurable instead of hardcoded. Instead of always using "Mike" as the team leader, the name can now be set dynamically, improving flexibility for different team configurations.Team leader name configuration:
team_leader_nameto theMGXEnvclass, allowing the team leader's name to be changed from the default ("Mike") as needed.publish_messagemethod to useself.team_leader_nameinstead of the hardcoded team leader name when retrieving the role.move_message_info_to_contentmethod to referenceself.team_leader_namewhen displaying message recipients, ensuring consistency with the configurable team leader name.