Skip to content

Bug: crash on 404 when resource ID type does not match query string #644

@bart-degreed

Description

@bart-degreed

Description

See #631 (comment)

Looking at the changes, the trim/split/findindex url parsing feels a bit brittle to me. Wouldn't it be an option to use the route values, like it is done at:

private ResourceContext GetCurrentEntity()
?

For example, the debugger shows me for the request path:

api/v3/users/ABC/completions

these route values:

{
  "action": "GetRelationship"
  "controller": "Users"
  "id": "ABC"
  "relationshipName": "completions"
}

Hope this helps.

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