Closed baptisteArno closed 1 year ago
Name | Link |
---|---|
Latest commit | 49c1d150dd63c249fb334dcc1af099786cc878f1 |
Latest deploy log | https://app.netlify.com/sites/docusaurus-openapi/deploys/6384e2a235a78200090ae810 |
Deploy Preview | https://deploy-preview-233--docusaurus-openapi.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
Is GlobExcludeDefault used anywhere else? Can we just add **/_category_.{json,yaml,yml}
to it so we donβt need to do the filtering or pushing of the _spec_
files?
True! That should work just fine π
Hmm it looks like the demo isnβt picking up the _spec_
π€
I didnβt realize the default glob is coming directly from Docusaurus, so maybe they changed their glob in a newer version?
That's a mystery for me, I checked the file history that contains the GlobIgnore pattern, it has never changed π€ I'll investigate and let you know
It's this pattern "**/_*/**"
that excludes _spec_.*
files.
Let's just not rely on GlobExcludeDefault
for this source fetching. It's useless.
Was discussed here: https://github.com/cloud-annotations/docusaurus-openapi/pull/107#discussion_r772093391
Closes #232