-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reference docs generation and plan. #319
Changes from all commits
3d81a3b
8649c2c
7a39578
7636472
e291209
1700d08
9498ef0
76dd5eb
1729517
e129117
c003a01
8a603f2
9b5baf6
b0cd4ae
bf62e87
97880ac
8e933df
265835e
27bcedb
1cf3051
e295273
66843f8
2a660b5
8372a2a
1ead074
2835357
2a3fb2b
4d59dd7
ee43790
4028c4e
97e77b4
673a256
4a3a2ea
a2a61c7
17f782d
cd24ff6
867d447
bdfc4d2
190e5b9
e84bc97
f1a87eb
46eaac2
de6e748
428ea26
1384092
c4161d9
5f29e13
881812b
08ed720
820b0b0
1c67fa2
8963395
879159f
9f66f90
18f05b3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,31 @@ | ||
# Hello sdk dev! | ||
|
||
This is your home base for how to develop on the project locally and process around that | ||
|
||
## Branches | ||
|
||
- `dev` | ||
in development | ||
- `main` | ||
"stable" what is on npm | ||
|
||
- `<name>/<issue_number>-<short_title>` (personal branches) | ||
for example `frankie/i123-docs` | ||
|
||
all PRS go into `dev` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should we make a comment about hotfix prs going straight to main? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nice. Those would be patch releases aye? i feel like we could make a patch branch. Basically anything we write ha gotta get smoke testing befor going into main + published... depends how many patches we expect. What I'm being cautious of is "special shorcuts". They can cause problems |
||
|
||
## Versions | ||
|
||
The SDK version must match a compatible [`entropy-core`](https://github.com/entropyxyz/entropy-core) version. | ||
|
||
<!-- TODO: --> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What's this here for? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. An invisible comment! i think I'd like to see a thing there where we list the details of the compatible versions of things. this was just from using other sdks where it became a nightmare to know how to run a compatible network of tools cos the versions of things which work together was not well documented. |
||
|
||
| module | tag | | ||
| ----------------- | ----------------- | | ||
| `@entropyxyz/sdk` | `main` TODO | | ||
| `entropy-core` | `release/v0.0.12` | | ||
|
||
|
||
## Tests | ||
|
||
For the tests to run you **must** edit your `/etc/hosts` file, adding: | ||
|
@@ -93,13 +119,32 @@ git commit --no-verify | |
|
||
## Publishing | ||
|
||
**Unfinished section** | ||
|
||
Always publish from `stable` branch | ||
|
||
- [ ] craft version pr for `dev` into `main` | ||
- [ ] `yarn burn` | ||
- [ ] `yarn build` | ||
- [ ] `yarn test` | ||
|
||
- change logs should be hand written as apart of the version pr | ||
- `yarn version patch #or major.minor.patch` | ||
|
||
<!-- TO-DO: figure out with him an automated system --> | ||
|
||
- [ ] minimum day ideally two day before ping @johnnymatthews on version bump pr set 48 hour timer | ||
- [ ] after timer merge into main | ||
- [ ] `git push origin main --tags` | ||
- [ ] make sure we have a version tag | ||
- [ ] check out version tag | ||
- [ ] create a tag push to main? this might be handled by yarn needs to be checked | ||
- [ ] `npm publish` | ||
|
||
```bash | ||
git checkout stable | ||
yarn burn | ||
yarn | ||
yarn build | ||
yarn version --patch # patch|minor|major | ||
npm publish | ||
git push origin stable --tags | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
/** @type {import('typedoc').TypeDocOptions} */ | ||
|
||
// see: https://typedoc.org/options/ | ||
|
||
module.exports = { | ||
// NOTE: entryPoints reflects pakcage.json "exports" | ||
entryPoints: [ | ||
'src/index.ts', | ||
'src/keys/index.ts', | ||
], | ||
// entryPointStrategy: 'expand', | ||
|
||
out: './docs', | ||
|
||
tsconfig: './tsconfig.json', | ||
excludePrivate: true, | ||
// excludeInternal: true, | ||
validation: { | ||
notExported: true, | ||
invalidLink: true, | ||
notDocumented: true, | ||
}, | ||
plugin: [ | ||
'@mxssfd/typedoc-theme', | ||
'typedoc-plugin-rename-defaults', | ||
'typedoc-plugin-merge-modules', | ||
// 'typedoc-plugin-missing-exports', | ||
], | ||
/* typedoc-plugin-missing-exports:*/ | ||
// internalModule: 'internal', | ||
// placeInternalsInOwningModule: true, | ||
|
||
/* typedoc-plugin-merge-modules: */ | ||
mergeModulesRenameDefaults: true, | ||
mergeModulesMergeMode: 'project', | ||
|
||
theme: 'my-theme', | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is issue number required for the branch name? Will this now be the new standard? More often than not, our branches don't include the issue number in the name, but rather required in the PR description prefixed by "closes" or "fixes" or something along those lines
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I copied this from notes from a call with frankie. I'm not sure I care about issue number.
Let's discuss