feat: content claims reads by default with fallback for old index sources #93
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.
Makes content claims used by default. If no index was found from content claims, the handler is returned wrapped with the old
withIndexerSources
andwithDagula
(old)Alternatively, we could add a new middleware and keep there the old ones. We could inspect in these middlewares if we have a dagula instance already, but I don't think that is a good way to go as we in the future can just drop this fallback