Update SDK POJOs to match server POJO implementations #195
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shaileshpadave
force-pushed
the
auto-sync-pojo
branch
2 times, most recently
from
befb396 to
a3dd433
Compare
shaileshpadave
force-pushed
the
auto-sync-pojo
branch
3 times, most recently
from
ac0f7d8 to
c227d93
Compare
…gration.chat_completion) to match server implementation
…gration.chat_message) to match server implementation
…gration.embedding_request) to match server implementation
…gration.index_doc_input) to match server implementation
…gration.indexed_doc) to match server implementation
…gration.llm_response) to match server implementation
…gration.llm_worker_input) to match server implementation
…gration.store_embeddings_input) to match server implementation
…gration.text_completion) to match server implementation
…gration.vector_db_input) to match server implementation
…gration.category) to match server implementation
…gration.integration) to match server implementation
…gration.integration_api) to match server implementation
…gration.integration_def) to match server implementation
…gration.prompt_template_test_request) to match server implementation
….access_key_response) to match server implementation
…table) to match server implementation
…_response) to match server implementation
…_summary) to match server implementation
…flow_test_request) to match server implementation
…ch_result) to match server implementation
…flow) to match server implementation
…flow_summary) to match server implementation
…t_handler) to match server implementation
…ma_def) to match server implementation
…_type) to match server implementation
…rnal_storage_location) to match server implementation
…rity.access) to match server implementation
…gration.config_key) to match server implementation
… to match server implementation
…rity.resource_type) to match server implementation
…gration.integration_def_form_field) to match server implementation
…rity.subject_type) to match server implementation
shaileshpadave
force-pushed
the
auto-sync-pojo
branch
from
ebae58f to
771ffb9
Compare
| type IntegrationApi struct { | ||
| Api string `json:"api,omitempty"` | ||
| Configuration map[string]interface{} `json:"configuration,omitempty"` | ||
| Configuration map[ConfigKey]interface{} `json:"configuration,omitempty"` |
There was a problem hiding this comment.
modification - backward compatibility ?
Contributor
Author
There was a problem hiding this comment.
Good one! we should maintain bc. thanks
orkes-harshil
approved these changes
Jun 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR updates multiple SDK POJOs to match the corresponding server implementations.
Automatically generated by Conductor workflow using LLM assistance.
NOTE : Either added new member to model or created new model altogether so backward compatibility is maintained.