X Tutup
Skip to content

fix: Preserve content-type when present in SPARQL accessor#2126

Merged
joachimvh merged 1 commit intoCommunitySolidServer:versions/next-majorfrom
elf-pavlik:meta-in-sparql
Mar 3, 2026
Merged

fix: Preserve content-type when present in SPARQL accessor#2126
joachimvh merged 1 commit intoCommunitySolidServer:versions/next-majorfrom
elf-pavlik:meta-in-sparql

Conversation

@elf-pavlik
Copy link
Contributor

📁 Related issues

✍️ Description

I wrote a HybridDataAccessor that has rdfAccessor that stores all the RDF, containers and metadata - in my case in SPARQL endpoint, and binaryAccessor that stores non-RDF. Im my case it uses S3 API and open source Garage as object storage. Since I store metadata for everyting in SPARQL I need to be able to the original content type that was stored. This PR prevents it from being overwritten

✅ PR check list

Before this pull request can be merged, a core maintainer will check whether

  • this PR is labeled with the correct semver label
    • semver.patch: Backwards compatible bug fixes.
    • semver.minor: Backwards compatible feature additions.
    • semver.major: Breaking changes. This includes changing interfaces or configuration behaviour.
  • the correct branch is targeted. Patch updates can target main, other changes should target the latest versions/* branch.
  • the RELEASE_NOTES.md document in case of relevant feature or config changes.
  • any relevant documentation was updated to reflect the changes in this PR.

Discussed with @joachimvh https://matrix.to/#/!FYRTVjiUaXQvzzfwZM:gitter.im/$G7qk6H9tmDdTWgFPcLwttEw0ziqphVFaV0j4VRYm870?via=gitter.im&via=matrix.org&via=matrix1.link

Im working with 8 alpha packages and build OCI images in CI that use that version. I'm targeting versions/next-major hoping that it could be relased to npm after it's merged 🤞

@joachimvh joachimvh merged commit 8575af4 into CommunitySolidServer:versions/next-major Mar 3, 2026
18 checks passed
@elf-pavlik elf-pavlik deleted the meta-in-sparql branch March 3, 2026 12:46
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.

2 participants

X Tutup