How to use gatsby-source-contentful's enableTags with a Tag content model

[bartveneman]

My website uses Contentful and we've had a Tag since it's inception (many years ago). Contentful and gatsby-source-contentful now also support Contentful's own tags feature when using enableTags in the pluginOptions. However, a gatsby build fails because of the conflict between the content model and Contentful's own tags. Apparently this is expected as I found out in the test suite.

My question:

How am I supposed to work around this?

I currently see these options:

1. 'Rename' our Tag content model (create a new model, copy all entries and links, remove old entries, remove old links, remove old model). Quite a few steps and error prone.
2. Change usenameForId to true and rename my Tag model to Whatever Tag (and update many occurences of content models that have different names than their ID's)
3. Create a PR to add an extra option in gatsby-source-contentful to allow Contentful's Tag to be renamed to something else to avoid conflicts.
4. Upgrade to gatsby-source-contentful@next and hope that resolves the issues?

Does anyone have additional input for this? Am I missing something?

[bartveneman]

It turns out the next gatsby-source-contentful will fix this problem! #31385 (comment)

The old naming pattern for generated node types based on your Contentful content model was pretty simple. This gave us shorter queries, but came with restrictions for content type names. Content type names like entity, reference, tag, asset did cause problems or simply did not work.

Instead of doing this on a collision, we always prefix for consistency.