Skip to content

Better separate SparqlTriple and SparqlTripleSimple types to avoid accidental mismatches #3179

Better separate SparqlTriple and SparqlTripleSimple types to avoid accidental mismatches

Better separate SparqlTriple and SparqlTripleSimple types to avoid accidental mismatches #3179

Triggered via pull request April 29, 2025 10:29
Status Failure
Total duration 25s
Artifacts

codespell.yml

on: pull_request
Check for spelling errors
19s
Check for spelling errors
Fit to window
Zoom out
Zoom in

Annotations

1 error
Check for spelling errors: src/parser/SparqlTriple.h#L107
retreive ==> retrieve