-
Notifications
You must be signed in to change notification settings - Fork 22
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
chore: split packages/access-client/src/capabilities to new package @web3-storage/capabilities #218
Conversation
…m @web3-storage/capabilities
Deploying with Cloudflare Pages
|
…the respective package, not all of them
…ntains packages/capabilities
…d packages/capabilities" This reverts commit 285c177.
bd0bfe7
to
e60626c
Compare
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.
Most comments are suggestions, feel free to address or disregard. I don't think we need another review cycle even if you choose to address them.
Co-authored-by: Irakli Gozalishvili <contact@gozala.io>
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.
made a PR with fixes for my inline comments #239
@@ -28,7 +28,7 @@ jobs: | |||
node-version: 18 | |||
cache: 'pnpm' | |||
- run: pnpm install | |||
- run: pnpm run build | |||
- run: pnpm -r --filter @web3-storage/access run build |
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.
actually now it need to be pnpm run build
because access-client depends on capabilities
strategy: | ||
matrix: | ||
pnpm-version: | ||
- 7 | ||
node-version: | ||
- 18 | ||
package: | ||
- capabilities |
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.
why matrix ?
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.
it's what @Gozala had done in the code snippet he linked me to in his review :)
- name: Typecheck | ||
uses: gozala/typescript-error-reporter-action@v1.0.8 | ||
with: | ||
project: packages/${{matrix.package}}/tsconfig.json |
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 really do not like this action, it makes reviews harder if there are any ts errors, like reviewing a draft PR and pnpm run lint
already does typechecking
uses: gozala/typescript-error-reporter-action@v1.0.8 | ||
with: | ||
project: packages/${{matrix.package}}/tsconfig.json | ||
- run: pnpm -r --filter @web3-storage/${{matrix.package}} run lint |
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.
needs - run: pnpm -r --filter @web3-storage/${{matrix.package}} run build
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.
ok I removed it based on this
@@ -28,7 +28,7 @@ jobs: | |||
node-version: 18 | |||
cache: 'pnpm' | |||
- run: pnpm install | |||
- run: pnpm run build | |||
- run: pnpm -r --filter @web3-storage/upload-client run build |
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.
revert this please, running build for all packages catches errors that local build doesnt
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.
looks like you reverted it. lmk if there's something more I should do
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.
no all of it is in #239
"test:node": "mocha 'test/**/!(*.browser).test.js' -n experimental-vm-modules -n no-warnings", | ||
"test:browser": "playwright-test 'test/**/!(*.node).test.js'", |
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.
do we have browser or node specific tests in this package ?
}, | ||
"eslintConfig": { | ||
"extends": [ | ||
"./node_modules/hd-scripts/eslint/preact.js" |
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.
this should be "./node_modules/hd-scripts/eslint/index.js"
…web3-storage/capabilities (#218) Motivation: * #80 To do: * [x] initial package split * [x] remove capabilities dir from packages/access-client and fix imports in access-client * [x] fix imports from other packages that were importing from access-client/capabilities * [x] consider splitting to `capabilities/{service}/types` not `capabilities/types` * decided not to unless requested (makes exports map even more complicated, can do later) * [x] GH actions should run tests on packages/capabilities * [x] .github/workflows/release.yml does npm/docs jobs if paths_released contains packages/capabilities Co-authored-by: Irakli Gozalishvili <contact@gozala.io>
Motivation:
To do:
capabilities/{service}/types
notcapabilities/types