I haven’t given it that much thought, so take it with a grain of salt. Definitely wouldn’t need to be part of the repo. I just thought that if the API evolves in the SN app, having a library as part of the same repo would help keep it in sync. Like a monorepo where one package is published as a lib to npm
I was thinking things like type declarations for resources, etc
Ah, I see! Could also be a "reference implementation"
reply
Yes, exactly!
reply