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
Everything feels like it's working so far but in GraphiQL we find that allFile query will fail indicating something's not right.
I think it'd be helpful to let the user know that the path is invalid while (re)building but will defer to the team on what the right solution should be.
The text was updated successfully, but these errors were encountered:
* upstream/master: (156 commits)
Publish new version
Publish
use peer reps (gatsbyjs#2832)
escape pipe in markdown (gatsbyjs#2835)
Publish
Small, perhaps nitpicky, change but not explicitly stating which file this config was referencing tripped up the flow for me for a bit when running through step-by-step. (gatsbyjs#2834)
Fix no trailing slashes (gatsbyjs#2828)
Publish
Update to the latest Prettier
Small fixes to tutorial part one (gatsbyjs#2821)
Revert "Fix: only the first feed was getting options.query injected. Now all the feeds have it injected. (gatsbyjs#2571)" (gatsbyjs#2820)
Revert "Added the ability to customize the feed's title (gatsbyjs#2573)" (gatsbyjs#2822)
keep track of root node id with weakmap instead of storing root node id as additional field in sub nodes (gatsbyjs#2812)
Publish
Add onLoad prop to gatsby-image (gatsbyjs#2818)
Add post "Migrate from Hugo to Gatsby" (gatsbyjs#2808)
Update readme showcase so that source links are distinct (gatsbyjs#2815)
Publish
Add Softin Sistemas' website into Showcase (gatsbyjs#2793)
Validate that gatsby-source-filesystem paths exist fixesgatsbyjs#2806 (gatsbyjs#2813)
...
mwfrost
pushed a commit
to mwfrost/gatsby
that referenced
this issue
Apr 20, 2023
While specifying path in
gatsby-config.js
validate thepath
and let the user know if it doesn't exist instead of failing quietlye.g.
> gatsby develop
Everything feels like it's working so far but in GraphiQL we find that
allFile
query will fail indicating something's not right.I think it'd be helpful to let the user know that the path is invalid while (re)building but will defer to the team on what the right solution should be.
The text was updated successfully, but these errors were encountered: