-
Notifications
You must be signed in to change notification settings - Fork 113
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
Migrate getVersion
GraphQL Request to REST
#2221
Comments
is this a part of the remove ET PR or is it something we plan to do before we merge the remove ET PR ? |
hey @rashidakanchwala this is just a tech debt in general. It's related to getVersion in flowchart. It doesn't block ET removal |
but if we remove graphQL entirely, we won't be able to getVersion right? |
hey @rashidakanchwala yeah that's correct. Therefore GraphQl is not fully removed yet. So far we only removed the part that related to ET. In order to remove graphQl completely, we need to migrate the Graphql to Rest, which is this ticket |
ok, great. I suggest let's do this small migration in the following sprint. Then when we remove ET, we remove entire GraphQL and all dependencies as well. Wdyt? |
Description
As part of our ongoing effort to remove all GraphQL dependencies related to Experiment Tracking, we found that the
getVersion
GraphQL request is in the flowchart. This task involves migrating thegetVersion
request to use REST so that we can remove GraphQL from the codebase entirely.Context
Transitioning to REST helps to simplify the architecture and remove GraphQL from the codebase completely
Checklist
The text was updated successfully, but these errors were encountered: