Fix reponse header parsing #11
Open
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.
First check if value can be converted to a number. If it can't, parse it as JSONString in the object instead of "" (JSONRaw)
Update line 304
Set Variable [ $jsonType ; Value: Case ( GetAsNumber ( $split ) = $split ; "" ; JSONString ) ]Why?
When requesting an exact count from Supabase, the result is returned in a header like:
Content-Range: 0-24/3573458But when parsing this into a JSON object, the default FileMaker behavior just returns this as
{"Content-Range": 0}It's likely a very rare edge case because the value is compatible with "evaluate" and the result of that expression would be 0, but since we need it as a string, the better solution is to force the value back as a JSONString if it's not strictly a number