Skip to content

Member resolver: let a resolver also map keyword names #34

Closed

Description

@b-re-w

Follow-up to #17. A member resolver maps a member name (fill_max_width -> fillMaxWidth), but keywords on proxy methods stay Kotlin names (m.padding(paddingValues=...)), while pythonx-compose already maps keywords for module-level functions.

Decided: a resolver may return (kotlin_name, keyword_map) instead of kotlin_name, where keyword_map is {python_kw: kotlinParam} applied when calling that member. Returning a plain name keeps today's behaviour. The binder still renames nothing on its own.

Completion: m.padding(padding_values=...) works with a resolver that returns a keyword map; an unknown keyword still raises TypeError naming the Kotlin parameters; with no resolver, behaviour unchanged; tamper check.

Activity

  1. b-re-w commented on Oct 3, 2026

    @b-re-w
    MemberAuthor

    Landed in develop via #51.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions