Skip to content

Add support for writing non partial data #30

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 1 commit into from
Sep 3, 2024
Merged

Conversation

DerAndereAndi
Copy link
Member

When the remote service does not provide support for partial writes, it is required that all data is always written. Which means that the changed data has to be merged with the currently known remote data, or that the full data is provided in the write in the first place.

This commit adds support for a merge, if merge support is implemented. Otherwise it will return an error, and the data will be sent as is.

When the remote service does not provide support for partial writes, it is required that all data is always written. Which means that the changed data has to be merged with the currently known remote data, or that the full data is provided in the write in the first place.

This commit adds support for a merge, if merge support is implemented. Otherwise it will return an error, and the data will be sent as is.
@DerAndereAndi DerAndereAndi added the enhancement New feature or request label Sep 1, 2024
@coveralls
Copy link

Coverage Status

coverage: 93.551% (+0.001%) from 93.55%
when pulling b691402 on feature/full-write
into 852045e on dev.

@DerAndereAndi DerAndereAndi merged commit dd82619 into dev Sep 3, 2024
6 checks passed
@DerAndereAndi DerAndereAndi deleted the feature/full-write branch September 3, 2024 07:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants