Open frankiebee opened 2 months ago
try catch all promise and throw help full errors please π
or catch, add context and throw again!
promise
.catch(err => throw Error(err, { cause: "you forgot the endpoint!" })
cc @johnnymatthews
Could this end up in a Wiki? It's kinda a checklist + a guide + process
This needs to be defined but to kick off the conversation heres what i think we should do in the near future i'm open to negotiations so feel free to comment. on any step we can open appropriate issues from here:
kinds of docs
[ ] Inline ([in code] auto generated method docs)
ideally we have some kind of bot to make sure devs are updating inline docs i guess thats @johnnymatthews for now π
[ ] High level usage docs (hand written) these kinds of docs can clutter code so they need a dedicated home lets figure that out my proposal is we have sdk/docs/examples that when updated get copied over to the docs repo so we arent responsible for hosting. @johnnymatthews will do this by hand for now and we'll figure out whats best when ready p.s.: @jawn we need to figure out how thats on the website? i guess that may also already be figured out and maybe @johnnymatthews already know about it?
[ ] Run time docs
[ ] Contributing docs
[ ] Commits / branches / tags
name/issue-number#tittle
release/v-name
v-name
||v
? @jawndiego read https://semver.org/ we will follow this when are major version is 1"stable"
includes @johnnymatthewshot-fix
does not need @johnnymatthews unless include docs but really should just link an issueprerelease
is the version branchside note
Publish process: (for dev readme)
yarn burn
yarn bundle
yarn test
npm publish