Logan Anderson

Sorry for the delayed reply, thanks @danielknell for submitting this issue. I believe that #3198 will be a potential fix for this.

# Quick update. #3198 has been merged. So you can test to see if this is fixed now by installing `tinacms@beta` and `@tinacms/cli@beta`.

This _could_ be a fix: https://github.com/tinacms/tinacms/pull/2099

Perhaps this could be solved with a migration tool? See tinacms/tina-graphql-gateway#235

@jamespohalloran I was just looking into this and I can not reproduce in the mono repo. I did however find an issue that may be causing it. It looks like...

@brvnonascimento I like this idea. We currently do this for each collection so you can write queries [like this](https://github.com/tinacms/tina-cloud-starter/blob/main/.tina/queries/queries.gql#L24) what would be the use case for doing this at the...

> I believe step 3 is so that You can use this standalone approach with contextual editing (Seems like this may go away with the iframe approach later though). If...

@jamespohalloran > If this was an opt-in feature, I'd say it can wait. It seems like it's going to impact the performance for all sites though which might be a...

PR and npm tag have been update based on your comments @jamespohalloran

@danielknell I like this idea as well. Here is a work around that is also hacky but works. ```ts import router from 'next/router' //... cmsCallback: (cms) => { // ......