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
reply
Ah, I see! Could also be a "reference implementation"
reply
Yes, exactly!
reply
You sneak in a lot of content in edits that I miss! I definitely think API keys would be a good enhancement, but probably not necessary up front.
reply
I know, it's a disease 🙈 lol
reply
I'm like this too, it's so strange how different a text is while it is editable, versus when it is "set in stone". I hear many writers / editors say this too, they will often write on a computer, but then print out the text and read it on paper, in order to improve it!
I wonder why our brains work like that. Something to do with "you can't make bets with money you don't have" I think. Easy to approve of a text while you can directly control it.
reply
I just need to wait to reply to you til 10 minutes is up lol
reply
.env
file./api/auth/session
regularly would be enough to keep the session alive but doesn't seem so)