Skip to content

Conversation

@ae0n
Copy link

@ae0n ae0n commented Jun 27, 2025

Include oneof field names in conflict detection to properly generate root prefixes when oneof fields conflict with imported package names.
Closes #1911

@i-am-the-slime
Copy link
Contributor

@thesamet do you think we should fork the library?

@thesamet
Copy link
Contributor

@i-am-the-slime help in maintenance could be appreciated. The PR did not run should CI tests for some reason. I was trying yesterday to see if this is related to mergify and made some related changes. Can you take a look?

Include oneof field names in conflict detection to properly generate
_root_ prefixes when oneof fields conflict with imported package names.
@thesamet thesamet force-pushed the fix-incorrect-import-generation-for-oneof branch from 023d59c to 91836b8 Compare August 20, 2025 04:53
i-am-the-slime added a commit to i-am-the-slime/ScalaPB that referenced this pull request Aug 22, 2025
The test was using OneofImportConflict but the generated class
is OneofImportConflictTest. This fixes the compilation error
in the e2e tests for PR scalapb#1912.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
@i-am-the-slime
Copy link
Contributor

I tried to address this with some AI help here: #1947
I was hoping I could have CI run until I see if it works but it needs approval.

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.

ScalaPB generates incorrect import paths for oneof fields when field name conflicts with imported package

3 participants