URL to save solidDataset
to.
The [[SolidDataset]] to save.
Optional
options: Partial<Optional parameter options.fetch
: An alternative fetch
function to make the HTTP request, compatible with the browser-native fetch API.
options.prefixes
: A prefix map to customize the serialization. Only applied on resource creation if the serialization allows it.
A Promise resolving to a [[SolidDataset]] containing the stored data, or rejecting if saving it failed.
Given a SolidDataset, store it in a Solid Pod (overwriting the existing data at the given URL).
A SolidDataset keeps track of the data changes compared to the data in the Pod; i.e., the changelog tracks both the old value and new values of the property being modified. This function applies the changes to the current SolidDataset. If the old value specified in the changelog does not correspond to the value currently in the Pod, this function will throw an error (common issues are listed in the documentation).
The SolidDataset returned by this function will contain the data sent to the Pod, and a ChangeLog up-to-date with the saved data. Note that if the data on the server was modified in between the first fetch and saving it, the updated data will not be reflected in the returned SolidDataset. To make sure you have the latest data, call [[getSolidDataset]] again after saving the data.
The Solid server will create any intermediary Containers that do not exist yet, so they do not need to be created in advance. For example, if the target URL is https://example.pod/container/resource and https://example.pod/container/ does not exist yet, it will exist after this function resolves successfully.