Skip to content

bug in mappers logic when using middleware #13

Open
@AmadoGuerrero

Description

@AmadoGuerrero

If you don't use middleware, there is no problem, the mappers work fine.
But if you decide to use middlware to verify if the projectId is valid (like I did) you will run across a bug because the projectToBody mapper function will get called twice. (Once when checking the id, and another when returning the updated field). so when intToBoolean runs the second time, it will be comparing true/false to 1 and that will always be false (even if the action has been completed). I had to change line 9 in mappers.js from return int === 1 ? true : false; to return int === 1 || int === true ? true : false; for it to work for me.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions