Repository navigation
Two-argument expressions: no spaces allowed, and brackets needed in GET - #94
Open
BjarteMell wants to merge 1 commit into
Open
BjarteMell wants to merge 1 commit into
BjarteMell wants to merge 1 commit into
Conversation
The space breaks the expression in both GET and POST. Tested on SSB 07459. SCB TAB6471 behaves the same: `[top(2, 1)]` gives 400 and `[top(2,1)]` gives 200. Spaces in a plain list are fine (`valueCodes[Tid]=2024, 2025` works), so only spaces inside an expression fail. In a GET URL, an expression containing a comma must be wrapped in square brackets**, because a bare comma is the list separator. The guide hints at this in lines 924–926, but the sentence is incomplete: > If the value code should be surrounded by square brackets like `3,[1,2],4+5`.
runejo
reviewed
Oct 16, 2026
| You need to specify value codes for each variable that is not eliminable. The | ||
| value codes are given in a comma separated list. If the value code should be | ||
| surrounded by square brackets like `3,[1,2],4+5`. See bellow on how to specify | ||
| value codes are given in a comma separated list. If a value code or a selection expression contains a comma, wrap it in square brackets, e.g. `valueCodes[Tid]=[range(2002,2005)]` or `[top(5,1)]`. In a POST body, write the expression without brackets: `"range(2002,2005)"`. A bracketed string in POST is looked up as a value code and fails with `Non-existent value`. See bellow on how to specify |
Member
There was a problem hiding this comment.
This looks like a workarroud for a bug. Wrapping with [] does not make sense to me 🤔
Member
There was a problem hiding this comment.
to be clear these look wrong
[range(2002,2005)][top(5,1)]
runejo
reviewed
Oct 16, 2026
|
|
||
| ```sh | ||
| bottom(numberOfValues, offset) | ||
| bottom(numberOfValues,offset) |
Member
There was a problem hiding this comment.
removing spaces for the examples are good, but this also sounds like at bug we should fix in the API
This branch has not been deployed
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
2 participants
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.
The space breaks the expression in both GET and POST. Tested on SSB 07459. SCB TAB6471 behaves the same:
[top(2, 1)]gives 400 and[top(2,1)]gives 200. Spaces in a plain list are fine (valueCodes[Tid]=2024, 2025works), so only spaces inside an expression fail.In a GET URL, an expression containing a comma must be wrapped in square brackets**, because a bare comma is the list separator. The guide hints at this in lines 924–926, but the sentence is incomplete: