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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Server support] - Update CollectionsPage use-case to use Firebase Firestore/Authentication #144

Open
Tracked by #136
matuella opened this issue Jul 19, 2021 · 0 comments
Labels
enhancement New feature or changes to an existing one P1 Changes that should be worked now target: flutter Relates to Flutter and its sub-dependencies

Comments

@matuella
Copy link
Contributor

matuella commented Jul 19, 2021

Update CollectionsPage flow to use the new structure defined in both #143 and #146.

Ideally, these shouldn't require any changes, but there will be changes to the synchronicity of the events (like networking issues), so it's highly possible that the UI will also change.


Sub-issue that relates to the Server support - #136.

@matuella matuella added the needs triage Waiting for a responsible to categorize the issue label Jul 19, 2021
@matuella matuella changed the title [Server support] - Update CollectionsPage use-case to use Firestore. [Server support] - Update CollectionsPage use-case to use Firebase Firestore/Authentication Jul 19, 2021
@matuella matuella added target: flutter Relates to Flutter and its sub-dependencies new feature enhancement New feature or changes to an existing one and removed needs triage Waiting for a responsible to categorize the issue new feature labels Jul 19, 2021
@matuella matuella added the P1 Changes that should be worked now label Sep 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or changes to an existing one P1 Changes that should be worked now target: flutter Relates to Flutter and its sub-dependencies
Projects
None yet
Development

No branches or pull requests

1 participant