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
I have a schema named opinion referencing another called topic. The generated code is referencing a Main type that isn't exported which is causing tsc to fail:
Before reaching this stage, I learned a lot examining the source of linkat (many thanks to @mkizka). From there I copied postinstall.sh that handles downloading and generating com.atproto.repo schemas that are required by the generated api and the app/global.d.ts file declaring multiformats/cid to "fix" Could not find a declaration file for module 'multiformats/cid' errors.
Is there a better way to handle all that or any other guidance that someone could point me towards?
I've also looked into statusphere-example-app but it looks like it faces the same problem:
Thanks in advance!
The text was updated successfully, but these errors were encountered:
Describe the bug
I have a schema named opinion referencing another called topic. The generated code is referencing a
Main
type that isn't exported which is causing tsc to fail:To Reproduce
Steps to reproduce the behavior:
git clone [email protected]:pdandradeb/atproto-lex-test.git
cd ./atproto-lex-test && npm install
npm run typecheck
Expected behavior
API files generated without type errors.
Details
Additional context
Before reaching this stage, I learned a lot examining the source of linkat (many thanks to @mkizka). From there I copied
postinstall.sh
that handles downloading and generatingcom.atproto.repo
schemas that are required by the generated api and the app/global.d.ts file declaringmultiformats/cid
to "fix"Could not find a declaration file for module 'multiformats/cid'
errors.Is there a better way to handle all that or any other guidance that someone could point me towards?
I've also looked into statusphere-example-app but it looks like it faces the same problem:
Thanks in advance!
The text was updated successfully, but these errors were encountered: