Skip to content

Conversation

@FroggyRocky
Copy link
Contributor

add graphql support to all existing routes

@FroggyRocky
Copy link
Contributor Author

I added graphql route that essentially has a relay middleware that transforms requests in the way that allows us to use existing controllers initially created for REST. This way we wound't have to worry about synchronizing REST vs graphql in case we change/add additional behaviors to controllers.

@gitfrosh I just want you to see the approach, in case you approve it, I will promptly add pagination params in the request arguments + auth middleware

@FroggyRocky
Copy link
Contributor Author

pagination and authorization added ✅

@FroggyRocky
Copy link
Contributor Author

FroggyRocky commented Oct 23, 2024

this addresses issue #16

@FroggyRocky FroggyRocky marked this pull request as draft October 26, 2024 13:20
@FroggyRocky FroggyRocky marked this pull request as ready for review October 26, 2024 13:21
@MateuszKikmunter
Copy link
Collaborator

@gitfrosh please take a look at this one too

@gitfrosh
Copy link
Owner

gitfrosh commented Nov 2, 2025

Hi @FroggyRocky, thanks a lot for your contribution! It would be great to have a basic documentation on how to use the new endpoint. Also while testing locally, I get a 401 when calling /graphql. Any ideas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants