Add a safety check about expressions and tokens #95
Conversation
This file contains 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
Gustry
force-pushed
the
server_expressions
branch
from
def9a4d to
30b9e6c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Draft PR linked to 3liz/lizmap-web-client#4922
There is an issue if LWC uses the text template, we can't extract expressions for now using the QGIS API.
We can define when to enable this kind of check.
QGIS Server has a similar environment variable called
QGIS_SERVER_ALLOWED_EXTRA_SQL_TOKENShttps://docs.qgis.org/3.34/en/docs/server_manual/config.html
NOT READY FOR REVIEW