Skip to content

Conversation

@pswaminathan
Copy link
Contributor

This solves two things:

  1. Previously we could not use select in e.g. package_name
    This is useful for having one target across multiple environments. e.g. package_name = select({"dev": "com.my.app.debug"}) But because these were macros, select was not being evaluated.
  2. Ergonomics of invoking multiple macros
    Now there is a single thing to do in the build file. This also reduces duplication: previously you had to specify package name twice.

This would be a breaking change to consumers, so I'm wary of that. But I'm not sure how many others would feel this to be a regression, so I would love to hear feedback.

This solves two things:

1. Previously we could not use `select` in e.g. `package_name`
    This is useful for having one target across multiple environments.
    e.g. `package_name = select({"dev": "com.my.app.debug"})`
    But because these were macros, select was not being evaluated.
2. Ergonomics of invoking multiple macros
    Now there is a single thing to do in the build file. This also
    reduces duplication: previously you had to specify package name
    twice.
@pswaminathan pswaminathan changed the title Convert macros to rules and consolidate into one Convert macros to rules and consolidate into one for Crashlytics Nov 11, 2025
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