Minor fix of xql paths in js to allow for compatibility with existdb >= 6.1.0 #29
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Due to a change in strictness in exisdb 6.1.0 in regards to how modules can be called (exist-db PR 4274), any routing to / execution of ediarum/modules/*.xql directly leads to the error: "No function call details were provided when trying to execute a Library Module" in all versions greater than 6.0.0
This PR tries to prevent this by routing to the project-specific path instead (as it was already the case in the function.js script for
json.xql, but not forload.xqlanddownload.xql).Disclaimer: my knowledge about ediarum, exisdtb and xquery is very limited, treat PR with care.