You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Workflow Request class is used to handle several parameters such as provision, use_case, reprovision, etc, which is becoming unnecessarily complex and can lead to backwards compatibility issues with previous versions when serializing the requests.
What solution would you like?
Create subclasses of the WorkflowRequest class to handle each parameter
The text was updated successfully, but these errors were encountered:
dbwiddis
added
v2.18.0
Issues targeting release v2.18.0
and removed
backlog
Good to have functionality not critical for next release
labels
Sep 18, 2024
Hello ! I am new to open-source projects. I am working as junior dev in c#/React, also have 3 year experience with Java. Can I work on this issue? Can you give me some more info? Thanks ! :)
Hello over here too, @boooby19! I see you posted on #905 so let's get started on that one for your first commit(s) as this one is a bit more involved with the OpenSearch codebase serialization mechanism.
Is your feature request related to a problem?
Currently the Workflow Request class is used to handle several parameters such as
provision
,use_case
,reprovision
, etc, which is becoming unnecessarily complex and can lead to backwards compatibility issues with previous versions when serializing the requests.What solution would you like?
Create subclasses of the WorkflowRequest class to handle each parameter
The text was updated successfully, but these errors were encountered: