You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
right now the tags in mdx files are stored as a comma seperated string. This is proving to be in-efficient in many ways.
we have to update the arrays to a YAML format (or something similar).
tags:
- Tag1
- Tag2
It turns out that when you update the array to a YAML format in mdx files, Gatsby automatically starts updating the schema.
But that is taking too long on my machine (more than 45 mins). I am guessing because we have so many nodes, not sure.
@dennyabrain maybe whenever you get time, you can try this out on your machine.
The text was updated successfully, but these errors were encountered:
@aatmanvaidya can you make a PR with changes so i just have to run npm run start to test this? I tried changing tags for one but it looks like having mixed types it not allowed. So i am guessing you've changed tags for all.
@dennyabrain even I just changed for one, and the updating schema started, but yes, my development server was already running then, so like
first I ran npm run develop
and then, I updated just one tag into YAML, and then the updating schema popped up in the terminal.
right now the tags in mdx files are stored as a comma seperated string. This is proving to be in-efficient in many ways.
we have to update the arrays to a YAML format (or something similar).
It turns out that when you update the array to a YAML format in mdx files, Gatsby automatically starts updating the schema.
But that is taking too long on my machine (more than 45 mins). I am guessing because we have so many nodes, not sure.
@dennyabrain maybe whenever you get time, you can try this out on your machine.
The text was updated successfully, but these errors were encountered: