🗑️ Discontinuing the Old GraphQL Playground #2263
Open
+343
−1,517
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per my conversation with Gert, following up from the single person that mentioned it in the discord, we want to stop supporting this playground:
https://tina-gql-playground.vercel.app/object-list-templates.
We weren’t aware this playground existed, and we have a better one.
It’s using an API in tina.io with a couple of very old packages, and we don’t believe it’s worth maintaining as Tina can be tested out via either:
🤖🤖🤖
This pull request involves the removal of deprecated packages and associated code cleanup. The changes mainly focus on removing old dependencies and the code that relies on them.
Dependency Cleanup:
package.json
: Removed deprecated@tinacms/datalayer-old
and@tinacms/graphql-old
packages.Code Removal:
pages/api/graphql.ts
: Removed the entire file, which included imports and usage of the deprecated@tinacms/datalayer-old
and@tinacms/graphql-old
packages, along with custom classes and logic for in-memory data handling and GraphQL query resolution.🤖🤖🤖
All New Content Submissions: (To be confirmed by reviewer)