Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Use version catalog for dependency management #185

Merged
merged 2 commits into from Aug 17, 2022

Conversation

oas004
Copy link
Contributor

@oas004 oas004 commented Jul 30, 2022

First of all, thanks for an awesome project! 馃ぉ I really like it!

In this PR I have tried to implement version catalog for dependency management. This is important to ensure consistency in library versions across modules.

There are some things to consider. The AGP version is not yet updated (7.0.4) and therefore [version catalog]
(https://docs.gradle.org/current/userguide/platforms.html) is still experimental. However, since there was a PR on
this (181) I thought this was okay. Then I can
rebase and remove the enableFeaturePreview flag when that is merged. Furthermore, I have not
implemented plugins in library.versions.toml as that is a feature that was added in version 7.2 of gradle.

Update: Rebased on #181, used plugins from version catalog and updated the root gradle file 馃槃


Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

  • Make sure to open a GitHub issue as a bug/feature request before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)

Fixes #172 馃
Fixes #160 馃

@oas004 oas004 force-pushed the feature/version-catalog branch 2 times, most recently from 4a6b6f5 to 5b84f6f Compare July 30, 2022 23:18
@oas004
Copy link
Contributor Author

oas004 commented Aug 3, 2022

@barbeau There is always one UI test that is failing, it runs green locally. Is it just a flaky test? Or is there something I can do to optimise this? 馃 馃槃

@barbeau
Copy link
Contributor

barbeau commented Aug 3, 2022

@oas004 it's a known issue with the test on CI at the moment. Please see #174.

@oas004
Copy link
Contributor Author

oas004 commented Aug 3, 2022

@oas004 it's a known issue with the test on CI at the moment. Please see #174.

Thanks for quick reply! That makes sense! I'll leave it be then as the tests are passing locally 馃槃

Copy link
Member

@arriolac arriolac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change looks great btw! It LGTM. Still need to figure out the flaky test but I think this should be good to merge so long as tests pass locally.

@arriolac arriolac assigned wangela and unassigned barbeau Aug 17, 2022
@wangela wangela merged commit b2b33ab into googlemaps:main Aug 17, 2022
googlemaps-bot pushed a commit that referenced this pull request Aug 17, 2022
# [2.6.0](v2.5.3...v2.6.0) (2022-08-17)

### Features

* Use version catalog for dependency management ([#185](#185)) ([b2b33ab](b2b33ab))
@googlemaps-bot
Copy link
Contributor

馃帀 This PR is included in version 2.6.0 馃帀

The release is available on:

Your semantic-release bot 馃摝馃殌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
5 participants