docs: remove no-longer-present signatures graphql#8916
docs: remove no-longer-present signatures graphql#8916
Conversation
after merge of firestore conversion it appears there are no more typescript types that have the signatures block for use in the old graphql used to build reference docs via gatsby remove the block and the website builds again
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Well, as expected firestore docs are now missing which is kind of a big deal, but the reference API in general is still built now, and Vercel no longer errors: https://react-native-firebase-git-mikehardy-fix-old-we-c6f5f6-invertase.vercel.app/reference |
|
One thought - if I merge this firestore docs will be rebuilt live from main and they will then disappear - currently because main hasn't build successfully firestore reference docs are still there 😅 Going to hold off for a moment until I can think of a better reference API website solution (still thinking github pages built directly from typedoc and then pointed to from vercel and/or docs.page at this point, since docs.page munges up the output) |
Description
after merge of firestore conversion it appears there are no more typescript types that have the signatures block for use in the old graphql used to build reference docs via gatsby
remove the block and the website builds again
Related issues
Release Summary
shouldn't trigger a release but looking at the generated reference docs on the PR build in vercel will be instructive
Checklist
AndroidiOSOther(macOS, web)e2etests added or updated inpackages/\*\*/e2ejesttests added or updated inpackages/\*\*/__tests__Test Plan
Check the Vercel deployment to see if it still looks "okay", where "okay" is not that great since the old reference site generator finds the new typescript modules impenetrable, c.f.:
Think
react-native-firebaseis great? Please consider supporting the project with any of the below:React Native FirebaseandInvertaseon Twitter