Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@zazuko/trifid-plugin-ckan@4.0.0
Major Changes
Minor Changes
Patch Changes
trifid-core@3.0.0
Major Changes
849fa3d: Health check is now exposed at
/healthz
instead of/health
4b515f8: Use 'plugins' instead of 'middlewares'
849fa3d: Trifid Plugins should return an object:
The factory should also be a promise.
Previously, the factory was a function that returned an Express middleware.
Since the move to Fastify, we are now returning an object with two methods:
defaultConfiguration
androuteHandler
.The
routeHandler
method should return a route handler function.The
defaultConfiguration
method should return the default configuration for the plugin.This allows the user to use the plugin with the default configuration or to override it.
This can be useful to simplify the Trifid configuration files.
d9963cd: Remove the
rewrite
middlewareMinor Changes
query
function that can be used in all plugins to perform a SPARQL query0
.Patch Changes
@zazuko/trifid-entity-renderer@1.0.0
Major Changes
Minor Changes
Patch Changes
trifid-plugin-graph-explorer@2.0.0
Major Changes
6583c86: The plugin is now using the new Trifid factory, which is a breaking change.
Assets are served under
/graph-explorer/assets/
and/graph-explorer/static/
instead of/graph-explorer-assets/
and/graph-explorer-static/
.4b515f8: Use 'plugins' instead of 'middlewares'
trifid-handler-fetch@3.0.0
Major Changes
4b515f8: Use 'plugins' instead of 'middlewares'
0eaf2b7: Completely change the way it is working.
Instead of being an handler that is made to be called only when dereferencing, it is now a Trifid plugin that is exposing a new endpoint
/query
(for example) that can be used to perform SPARQL queries against the dataset.This means that it is now possible to perform SPARQL queries against a dataset that is loaded from a URL, which was not possible before.
This also means that it is possible to use all other Trifid plugins that were only working with a SPARQL endpoint and not with a dataset coming from a simple file.
Please take a look on how to use it in the documentation here: https://github.com/zazuko/trifid/tree/main/packages/handler-fetch#readme
293d7e6: The plugin is now using the new Trifid factory, which is a breaking change.
Patch Changes
unionDefaultGraph
configurationtrifid-plugin-i18n@3.0.0
Major Changes
@zazuko/trifid-plugin-iiif@1.0.0
Major Changes
Minor Changes
@zazuko/trifid-markdown-content@2.0.0
Major Changes
Patch Changes
@zazuko/trifid-plugin-sparql-proxy@2.0.0
Major Changes
Patch Changes
trifid-plugin-spex@2.0.0
Major Changes
trifid@5.0.0
Major Changes
trifid-handler-sparql
packageMinor Changes
Patch Changes
trifid-plugin-yasgui@3.0.0
Major Changes