Skip to content
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

[FEA]: message_type argument to DeserializeStage should be an enum #1835

Closed
2 tasks done
dagardner-nv opened this issue Aug 7, 2024 · 1 comment
Closed
2 tasks done
Labels
feature request New feature or request

Comments

@dagardner-nv
Copy link
Contributor

Is this a new feature, an improvement, or a change to existing functionality?

Improvement

How would you describe the priority of this feature request

High

Please provide a clear description of problem this feature solves

Currently the type for this argument is the class itself. However if it were an enum, then our CLI tool will be able to handle it as a CLI arg.

Describe your ideal solution

Refer to #1834

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
  • I have searched the open feature requests and have found no duplicates for this feature request
@dagardner-nv dagardner-nv added the feature request New feature or request label Aug 7, 2024
@dagardner-nv dagardner-nv changed the title [FEA]: message_type argument to DeserializeStage should be an Enum [FEA]: message_type argument to DeserializeStage should be an enum Aug 7, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in Morpheus Boards Aug 7, 2024
@dagardner-nv
Copy link
Contributor Author

Closing as MultiMessage is slated for removal in 24.10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
Status: Done
Development

No branches or pull requests

1 participant