Skip to content

Support preserving original package when remapping illegal names#1021

Open
JamesBraver wants to merge 1 commit into
Col-E:masterfrom
JamesBraver:master
Open

Support preserving original package when remapping illegal names#1021
JamesBraver wants to merge 1 commit into
Col-E:masterfrom
JamesBraver:master

Conversation

@JamesBraver
Copy link
Copy Markdown

  • Add mapClass(info, mapPackage) to NameGenerator to control package remapping.
  • Implement package-aware naming in AlphabetNameGenerator and IncrementingNameGenerator.
  • Introduce shouldMapPackage in NameGeneratorFilter and all filter implementations to decide whether a class's package should be remapped.
  • Update MappingGenerator and IllegalNameMappingTransformer to use the new package mapping logic.
  • Fix argument order in getMappedFieldName/getMappedMethodName calls within IllegalNameMappingTransformer.
  • Add tests verifying that illegal class names are remapped while keeping legal packages intact.

What's new

  • I don't know.

What's fixed

  • I don't know.

- Add `mapClass(info, mapPackage)` to `NameGenerator` to control package remapping.
- Implement package-aware naming in `AlphabetNameGenerator` and `IncrementingNameGenerator`.
- Introduce `shouldMapPackage` in `NameGeneratorFilter` and all filter implementations to decide whether a class's package should be remapped.
- Update `MappingGenerator` and `IllegalNameMappingTransformer` to use the new package mapping logic.
- Fix argument order in `getMappedFieldName`/`getMappedMethodName` calls within `IllegalNameMappingTransformer`.
- Add tests verifying that illegal class names are remapped while keeping legal packages intact.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants