Skip to content

Follow OpenCRUD specification #1057

@Aurelsicoko

Description

@Aurelsicoko

What is the expected behavior?

We should follow the OpenCRUD specification for our GraphQL API. It will allow everyone to enjoy futures generic services like documentation (as Swagger does with REST API) and easily switch between different GraphQL APIs which are following the same specification.

Thank @schickling for the proposal! We'll add this to our roadmap and we'll certainly make the small changes when we'll develop the mutations part.


  • I'm sure that this issue hasn't already been referenced

Metadata

Metadata

Assignees

No one assigned

    Labels

    issue: feature requestIssue suggesting a new featureseverity: lowIf the issue only affects a very niche base of users and an easily implemented workaround can solve

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions