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.
In knex, db.insert(data, ['id']) returns an array of objects in the shape of [{ id }, { id }]. Referencing
rows[0]
gives you{ id }
, and that means we callthis._get({ id })
, when we meant to callthis._get(id)
. This still works! Because of knexify manages to turn that into a valid query, but I'm not sure that's intended? We just want to call_get(id)
from the get go. This doesn't really change the outcome, but confused me for a while when debugging another issue, and this change could prevent future problems in casefeathers-knex
orknex
code changes in some way.