A library to have your app interact with Firestore in Elm
Drills down document paths with a specific path name.
This function is aimed to be chanind with pipeline operators in order to build up document path.
firestore
|> Firestore.collection "users"
|> Firestore.collection "items"
|> Firestore.collection "tags"
|> Firestore.get
|> Task.attempt GotUserItemTagsOf course, you can make it a single string as well
firestore
|> Firestore.collection "users/items/tags"
|> Firestore.get
|> Task.attempt GotUserItemTagsUpdates configuration
A record structure for a document fetched from Firestore.
The next page token.
This token is required in fetching the next page offset by pageSize in list operation.
A record structure composed of multiple documents fetched from Firestore.
Data structure for query parameter in calling list operation.
Updates only specific fields. If the fields do not exists, they will be created.
An error type
This type is available in order to disregard type of errors between protocol related errors as Http_ or backend related errors as Response.
Data structure for errors from Firestore
Data type for Transaction
A time transaction commited at
Starts a new transaction.
Adds a new update into the transaction
model.firestore
|> Firestore.commit
(transaction
|> Firestore.update draft1
|> Firestore.update draft2
|> Firestore.update draft3
)
|> Task.attempt CommitedCommits a transaction, while optionally updating documents.
Only readWrite transaction is currently supported which requires authorization that can be set via Config.withAuthorization function.
Data type for Firestore