Skip to content

/read/match doesnt need user_type #288

@branden-jones

Description

@branden-jones

If each profile has the aforementioned properties ( see issue #287 ) then this is an already established endpoint that can be used but only...

IF we remove user_type ( preferred and recommended )

OR role is implemented within Profile Object ( but user_type seems to still be redundant and unnecessary )

Having the ability to quickly grab a single object or a simple array of objects cuts down on sorting and looping times as well as smaller amounts of data.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions