Skip to content

chore: test code generation#909

Draft
kridai wants to merge 2 commits intomainfrom
test-generation-conversations
Draft

chore: test code generation#909
kridai wants to merge 2 commits intomainfrom
test-generation-conversations

Conversation

@kridai
Copy link
Contributor

@kridai kridai commented Feb 13, 2026

Fixes

test conversation v2 generation for twilio-python

Checklist

  • I acknowledge that all my contributions will be made under the project's license
  • I have made a material change to the repo (functionality, testing, spelling, grammar)
  • I have read the Contribution Guidelines and my PR follows them
  • I have titled the PR appropriately
  • I have updated my branch with the main branch
  • I have added tests that prove my fix is effective or that my feature works
  • I have added the necessary documentation about the functionality in the appropriate .md file
  • I have added inline documentation to the code I modified

If you have questions, please file a support ticket, or create a GitHub Issue in this repository.

github-merge-queue bot pushed a commit to twilio/twilio-oai-generator that referenced this pull request Mar 24, 2026
<!--
We appreciate the effort for this pull request but before that please
make sure you read the contribution guidelines, then fill out the blanks
below.

Please format the PR title appropriately based on the type of change:
  <type>[!]: <description>
Where <type> is one of: docs, chore, feat, fix, test, misc.
Add a '!' after the type for breaking changes (e.g. feat!: new breaking
feature).

**All third-party contributors acknowledge that any contributions they
provide will be made under the same open-source license that the
open-source project is provided under.**

Please enter each Issue number you are resolving in your PR after one of
the following words [Fixes, Closes, Resolves]. This will auto-link these
issues and close them when this PR is merged!
e.g.
Fixes #1
Closes #2
-->

# Fixes #
Added two fixes

- Empty to_dict generation for nested object. This was happening due to
`json-name` not getting propagated to nested objects
- reserved Keyword for nested property fix. Should use name instead of
baseName, sInce name has the updated value for reserved keyword like
_from for from.

Code generated of conversation v2 here
twilio/twilio-python#909

### Checklist
- [x] I acknowledge that all my contributions will be made under the
project's license
- [ ] Run `make test-docker`
- [ ] Verify affected language according to the code change:
- [ ] Generate [twilio-java](https://github.com/twilio/twilio-java) from
our [OpenAPI specification](https://github.com/twilio/twilio-oai) using
the [scripts/build_twilio_library.py](./scripts/build_twilio_library.py)
using `python scripts/build_twilio_library.py
path/to/twilio-oai/spec/yaml path/to/twilio-java -l java` and inspect
the diff
    - [ ] Run `make test` in `twilio-java`
    - [ ] Create a pull request in `twilio-java`
- [ ] Provide a link below to the pull request, this ensures that the
generated code has been verified
- [ ] I have made a material change to the repo (functionality, testing,
spelling, grammar)
- [ ] I have read the [Contribution
Guidelines](https://github.com/twilio/twilio-oai-generator/blob/main/CONTRIBUTING.md)
and my PR follows them
- [ ] I have titled the PR appropriately
- [ ] I have updated my branch with the main branch
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] I have added the necessary documentation about the functionality
in the appropriate .md file
- [ ] I have added inline documentation to the code I modified

If you have questions, please create a GitHub Issue in this repository.
kridai added a commit to twilio/twilio-oai-generator that referenced this pull request Mar 24, 2026
<!--
We appreciate the effort for this pull request but before that please
make sure you read the contribution guidelines, then fill out the blanks
below.

Please format the PR title appropriately based on the type of change:
  <type>[!]: <description>
Where <type> is one of: docs, chore, feat, fix, test, misc.
Add a '!' after the type for breaking changes (e.g. feat!: new breaking
feature).

**All third-party contributors acknowledge that any contributions they
provide will be made under the same open-source license that the
open-source project is provided under.**

Please enter each Issue number you are resolving in your PR after one of
the following words [Fixes, Closes, Resolves]. This will auto-link these
issues and close them when this PR is merged!
e.g.
Fixes #1
Closes #2
-->

# Fixes #
Added two fixes

- Empty to_dict generation for nested object. This was happening due to
`json-name` not getting propagated to nested objects
- reserved Keyword for nested property fix. Should use name instead of
baseName, sInce name has the updated value for reserved keyword like
_from for from.

Code generated of conversation v2 here
twilio/twilio-python#909

### Checklist
- [x] I acknowledge that all my contributions will be made under the
project's license
- [ ] Run `make test-docker`
- [ ] Verify affected language according to the code change:
- [ ] Generate [twilio-java](https://github.com/twilio/twilio-java) from
our [OpenAPI specification](https://github.com/twilio/twilio-oai) using
the [scripts/build_twilio_library.py](./scripts/build_twilio_library.py)
using `python scripts/build_twilio_library.py
path/to/twilio-oai/spec/yaml path/to/twilio-java -l java` and inspect
the diff
    - [ ] Run `make test` in `twilio-java`
    - [ ] Create a pull request in `twilio-java`
- [ ] Provide a link below to the pull request, this ensures that the
generated code has been verified
- [ ] I have made a material change to the repo (functionality, testing,
spelling, grammar)
- [ ] I have read the [Contribution
Guidelines](https://github.com/twilio/twilio-oai-generator/blob/main/CONTRIBUTING.md)
and my PR follows them
- [ ] I have titled the PR appropriately
- [ ] I have updated my branch with the main branch
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] I have added the necessary documentation about the functionality
in the appropriate .md file
- [ ] I have added inline documentation to the code I modified

If you have questions, please create a GitHub Issue in this repository.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant