fix(api): ContextMapper now coerces the row ID to an int for proper comparison #954
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.
Overview
I've been having an issue where, after I add a Context and try to re-fetch all Contexts from
/ocs/v2.php/apps/tables/api/2/contexts/
, the response returned by the API is aContext[]
as expected, but the values are allnull
.Example from before fix
This issue was preventing me from properly reviewing pull requests, so I decided to look into it. The problem was found in
ContextMapper.php
, where the row IDs were of typestring
, and the context ID variable heldint
s. They were being compared using===
operator which, in addition to value, checks for type equivalence.string
andint
are not of the same type, so the comparison was failing, resulting innull
values.Upon further investigation and with help from @juliushaertl, it is thought that it is due to sqlite storing the id as a
string
by default. The solution here would be to cast the row ID to anint
so that the strict comparison succeeds and to maintain compatibility with sqlite.