Thiago Bellini Ribeiro

I found a way to fix this in #409 . Maybe with this we don't need to refactor the ordering code anymore? The refactoring discussion is going to continue on...

> due to alphabetical sorting when passing 'ordering' as variable. Can you confirm this behavior or is it actually me doing something wrong? I'm not sure on how apollo itself...

Hey @iacobfred and @oleo65 Wow, I did miss that issue when it got opened. I'm not really sure what might be happening, specially because after moving from graphene I stopped...

I know it is been a while :), but v0.10.0 has a permissions extension, which should cover all needs described in this issue: https://strawberry-graphql.github.io/strawberry-graphql-django/guide/permissions/

This should be fixed in [v0.10.0](https://github.com/strawberry-graphql/strawberry-graphql-django/releases/tag/v0.10.0)

> I think this PR can now be closed since #45 has now been merged thinking @bellini666 As far as I can tell, you are right. Closing it!

Tip: Use dressing.nvim: https://github.com/stevearc/dressing.nvim It does what `telescope-ui-select.nvim` does but better, having the priority to use telescope but falling back to others it if is not found, and also works...

OMG those "it happens sometimes" are the worst to debug T_T The only idea I have here is: in case @instil-chloe is using strawberry-django (based on the traceback, I'm assuming...

I like where this is going... Checking it today I'm wondering if we should alllow a list of type extensions instead of just one. Then when doing, `field = extension.on_field`...

> Is there any way to make the metadata visible in the query? @shmoon-kr what exactly do you mean by this? I'm not sure if I got it from your...