Repository navigation
Feat: Restore the binder's Pythonic names (snake_case members and keywords) - #138
Merged
Merged
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
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.
Closes #131
Feature restored (SPEC U-12, U-8, B-7; AGENTS §12.1 corrected: namespaces are never renamed, member/function/parameter names are converted). 238119b had removed this by over-reading §12.1.
padding_from_baseline__TextUnit), object functions (Arrangement.spaced_by), extension methods, properties (read/write) and all keyword arguments are reachable by snake_case; capitalised names and namespaces are unchanged; Kotlin names keep working and stay what dir() lists.toURLString->to_url_string); an ambiguous alias is not served.Verification (coordinator, after merging develop, separate modules): plugin 274/0, desktopTest 607/0, ksp artifact 35/0, app 79/0, compose 118 (one intermittent recomposition test failed in one run; the two recomposition test classes ran 4x alone and the full compose suite 2x on both this branch and develop with 0 failures), androidNative OK.