Skip to content

Conversation

@jmfayard
Copy link
Member

@jmfayard jmfayard commented Aug 26, 2021

Reported by @LouisCAD


Hello! I just tried to migrate a project that I freshly created from Android Studio BumbleBee Canary 9, selecting "Empty Compose Activity", and there was 2 problems:

  • The implementation "androidx.compose.ui:ui:$compose_version" line stayed as is, even though it has a corresponding built-in dependency notation (AndroidX.compose.ui).
  • The implementation "androidx.compose.ui:ui-tooling-preview:$compose_version" line became implementation "androidx.compose.ui:ui-tooling-preview:_", so the dependency version was replaced by the placeholder, unlike the other. That one doesn't have a built-in dependency notation BTW.

@jmfayard jmfayard requested a review from LouisCAD August 26, 2021 16:29
@LouisCAD
Copy link
Member

That's proving the point that regexes are not the ideal solution. It leads to assumptions being made, and potentially endless exceptions because it's not semantic.

That's good for a hotfix, but I'd like to spend some time revisiting the migration code to improve its reliability and its "resistance" to tricky cases.

@LouisCAD
Copy link
Member

BTW, there's a typo in the commit message (missing h for "has"), can you correct it and force-push on this branch before merging?

The assumption that the name of the maven coordinate has at least 3 characters was incorrect.

The group has at least 4 characters like "a.de" (and probably more).

This way we can still differentiate with "hh::mm:ss" which is not a valid maven coordinate
@jmfayard jmfayard merged commit 64aea8f into main Aug 26, 2021
@jmfayard jmfayard deleted the migration-ui-fix branch August 26, 2021 18:20
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.

3 participants