Skip to content

Get rid of source sets #47

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

Merged
merged 3 commits into from
Dec 14, 2024
Merged

Get rid of source sets #47

merged 3 commits into from
Dec 14, 2024

Conversation

DanielRendox
Copy link
Owner

@DanielRendox DanielRendox commented Dec 14, 2024

They were previously created to reduce the number of calls to the server during the development. But it is not convenient to manage source sets for this reason only. A simpler approach would be to simply configure the app to refetch the grocery database only on release. (The initial prepopulation will still fetch the data from the server, but only once).

They were previously created to reduce the number of calls to the server during the development. But it is not convenient to manage source sets for this reason only. A simpler approach would be to simply configure the app to refetch the grocery database only on release. (The initial prepopulation will still fetch the data from the server, but only once).
@DanielRendox DanielRendox force-pushed the get-rid-of-source-sets branch from 3d8074b to d9dd29e Compare December 14, 2024 21:46
@DanielRendox DanielRendox merged commit 76182fc into develop Dec 14, 2024
4 of 6 checks passed
@DanielRendox DanielRendox deleted the get-rid-of-source-sets branch December 14, 2024 21:47
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