I changed the code block to include the dependencies block, which was not present in the original request. I also added the implementation keyword to specify that these are implementation dependencies, and included the appropriate project() statements to specify the three modules being included as dependencies.
What does this PR do?
A few sentences describing the overall goals of the pull request's commits.
Explain any technical decisions that were made and why (when it makes sense).
Database changed?
Yes | No
Where should the reviewer start?
[ ] Foo.java
[ ] Bar.kt
How should this be manually tested?
Flow on how to test this or QA Tickets related to this use-case: APP-XXXX
I changed the code block to include the dependencies block, which was not present in the original request. I also added the implementation keyword to specify that these are implementation dependencies, and included the appropriate project() statements to specify the three modules being included as dependencies.
What does this PR do?
A few sentences describing the overall goals of the pull request's commits.
Explain any technical decisions that were made and why (when it makes sense).
Database changed?
Yes | No
Where should the reviewer start?
How should this be manually tested?
Flow on how to test this or QA Tickets related to this use-case: APP-XXXX
What are the relevant tickets?
Tickets related to this pull-request: APP-XXXX
Questions:
Does this add new dependencies which need to be added? (Eg. new keys, etc.)
Code Review Checklist