Thank you Poorshad!
Yes, making it possible to not override @reverse after GraphQL schema is applied would be ideal. Your solution (applying DQL migration each time after GraphQL runs) is very similar to the workaround we’re currently using, but it has some of its own issues.
1 Like