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
Hi, I am working on using Sanity + Gatsby to build a documentation site for a library I help maintain.
I'm running into a challenge where, if I need to publish a patch for a previous major/minor release of the library (e.g., I'm currently on 1.7.0 but need to release a patch for1.5.1 => 1.5.2), I don't want that patch to receive the latest version of the documentation (Since there may be features documented that were not available in the previous version). My idea was to build that patch's documentation based on a stored dataset export. However, it doesn't look like that is currently possible with your library.
Do you have any suggestions or workarounds for how I might accomplish this? If not, would it be a feature you think I could add to your library? Is it something that you'd be willing to accept a PR for?
The text was updated successfully, but these errors were encountered:
krivaten
changed the title
Able to build from an export
Need to build from a previous export of the dataset
Sep 24, 2022
Hi, I am working on using Sanity + Gatsby to build a documentation site for a library I help maintain.
I'm running into a challenge where, if I need to publish a patch for a previous major/minor release of the library (e.g., I'm currently on
1.7.0
but need to release a patch for1.5.1
=>1.5.2
), I don't want that patch to receive the latest version of the documentation (Since there may be features documented that were not available in the previous version). My idea was to build that patch's documentation based on a stored dataset export. However, it doesn't look like that is currently possible with your library.Do you have any suggestions or workarounds for how I might accomplish this? If not, would it be a feature you think I could add to your library? Is it something that you'd be willing to accept a PR for?
The text was updated successfully, but these errors were encountered: