-
Notifications
You must be signed in to change notification settings - Fork 1
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Extract dependencies #25
Conversation
11fe39f
to
336daa8
Compare
I'm not sure if it's direction we want to follow. Here are my arguments
It's a lot of work. I believe having only dependencies and its versions defined in separate Gradle script plugin. What are your thoughts? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
discussed internally. Further work to make dependabot available will be continued in #19
234c190
to
c271008
Compare
…ract_dependencies # Conflicts: # androidApp/build.gradle.kts # build.gradle.kts # domain/build.gradle.kts
Sorry, once again: why don't we use groovy file (which is supported by Dependabot) for declaring dependencies? |
Resolves #13
This PR introduce dependencies extraction, so we could maintain those in future development in easy way.
We have separate file
dependencies.gradle.kts
where all dependencies and versions are stored.Also we use
extra properties
so in future when it's available we could usedependabot