Tomasz Pluskiewicz
Tomasz Pluskiewicz
We need some built-in ways to support updating resources. We should consider how updating a resource complement that resource's `GET` handler. **UC 1: PUT to update existing resource using `kl:OwnGraphLoader`**...
The RFC stands is [Problem Details for HTTP APIs](https://datatracker.ietf.org/doc/html/rfc7807) Kopflos should come with default error handling to return JSON error documents extended with a JSON-LD `@context` We can adapt the...
@bergos I wonder if you have thoughts on processing requests which match more than one operation. Specifically, a common case will be `hydra:Collection` vs `hydra:Resource`. If both of those base...
Currently the rdf-loaders are internal to the middleware. It should be possible to attach custom loaders. Something like an optional callback with the registry as parameter: ```js const myLoader =...
Although not specifically related to this PR, now I'm noticing the lack of expressivity of the plugin interface: given a Koplos instance, it does something with it. We may examine...
To simplify implementing resources backed by a SPARQL query, I'd like to have a handler, possibly exported from a dedicated package, that would make it possible declaratively. For example ```turtle...
Once we load an API description, it should be the default behaviour and easy to use option for implementors to cascade configuration option, bottom-up. Given a tree structure like ```...
In the PoC, I had [shape](https://github.com/zazukoians/trippin/blob/cli/kopflos/core/shape/config.ttl) which I would use to generate a loong SPARQL query. This method can be useful when API triples are spread across multiple graph but...
I would like to be able to run `kopflos validate --path [path]` or `kopflos validate --endpoint [endpoint]` to check that the API description has no errors. Shapes TBD
I just stumbled upon a small problem with spaced encoded in query string parameters of IRI Template routes Spaces in query can be encoded as `%20` or `+`. In the...