fix: connection method is not async #222
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Deploying with
|
| Latest commit: |
71972fc
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://a9794b5c.ucan-protocol.pages.dev |
| Branch Preview URL: | https://fix-connection-method-not-as.ucan-protocol.pages.dev |
hugomrdias
approved these changes
Nov 30, 2022
alanshaw
pushed a commit
that referenced
this pull request
Dec 6, 2022
🤖 I have created a release *beep* *boop* --- ## [8.0.0](access-v7.0.2...access-v8.0.0) (2022-12-06) ### ⚠ BREAKING CHANGES * access-client store decoupling ([#228](#228)) * upgrade to `@ucanto/{interface,principal}`@^4.0.0 ([#238](#238)) * follow up on the capabilities extract ([#239](#239)) ### Features * **access-client:** cli and recover ([#207](#207)) ([adb3a8d](adb3a8d)) * follow up on the capabilities extract ([#239](#239)) ([ef5e779](ef5e779)) * Revert "feat!: upgrade to `@ucanto/{interface,principal}`@^4.0.0" ([#245](#245)) ([c182bbe](c182bbe)) * upgrade to `@ucanto/{interface,principal}`@^4.0.0 ([#238](#238)) ([2f3bab8](2f3bab8)) ### Bug Fixes * connection method is not async ([#222](#222)) ([0dd1633](0dd1633)) ### Code Refactoring * access-client store decoupling ([#228](#228)) ([a785278](a785278)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
gobengo
pushed a commit
that referenced
this pull request
Apr 11, 2023
gobengo
pushed a commit
that referenced
this pull request
Apr 11, 2023
🤖 I have created a release *beep* *boop* --- ## [8.0.0](access-v7.0.2...access-v8.0.0) (2022-12-06) ### ⚠ BREAKING CHANGES * access-client store decoupling ([#228](#228)) * upgrade to `@ucanto/{interface,principal}`@^4.0.0 ([#238](#238)) * follow up on the capabilities extract ([#239](#239)) ### Features * **access-client:** cli and recover ([#207](#207)) ([720dafb](720dafb)) * follow up on the capabilities extract ([#239](#239)) ([717fcaa](717fcaa)) * Revert "feat!: upgrade to `@ucanto/{interface,principal}`@^4.0.0" ([#245](#245)) ([197439e](197439e)) * upgrade to `@ucanto/{interface,principal}`@^4.0.0 ([#238](#238)) ([309aff0](309aff0)) ### Bug Fixes * connection method is not async ([#222](#222)) ([7c4e0b6](7c4e0b6)) ### Code Refactoring * access-client store decoupling ([#228](#228)) ([64c7496](64c7496)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Peeja
pushed a commit
to storacha/upload-service
that referenced
this pull request
Jan 17, 2025
Pulls example tests out to own dir so we can run the same test for each ui library! fixes: storacha#222 You can see it run in CI at https://github.com/web3-storage/w3ui/actions/runs/3901558574/jobs/6663550379#step:6:13 and you can try it out locally from this branch by running: ``` $ pnpm install # one time download of test browsers $ pnpx playwright install # fails for vanilla currently, but is ok, proceed. $ pnpm build:examples $ pnpm test:examples Scope: 20 of 33 workspace projects examples/test/playwright test$ playwright test [30 lines collapsed] │ [30/33] [webkit] › sign-up-in.spec.ts:4:3 › vue: sign in │ [31/33] [webkit] › uploads-list.spec.ts:4:3 › react: uploads list │ [32/33] [webkit] › uploads-list.spec.ts:4:3 › solid: uploads list │ [33/33] [webkit] › uploads-list.spec.ts:4:3 › vue: uploads list │ │ 33 passed (7s) │ To open last HTML report run: │ │ npx playwright show-report │ └─ Done in 7.6s ``` _note: the build fails currently as our vanilla examples fail to build currently, which is why we need these tests!_ Adds and updates run scripts to make it easy to run package or example tests. Most of the time we'd want to run package tests locally, so this is set as the default. ```bash # runs package tests $ pnpm test # builkd examples. must be run before test so the dist dir exits for each $ pnpm build:examples # run example test $ pnpm test:examples # serve examples, so you can poke around as a dev. $ pnpm serve:examples ``` Updates examples to produce relative URLs by setting `base: ''` in vite config. This allows us to serve all the examples from a single static server in the `examples` dir, and `serve` is added with a `serve.json` config to rewrite the paths so the `dist` dir is served for each example. Adds playwright config to fire up the example server Adds github workflow to set up and run the browser tests only if we make a change to the examples. We may change this to run for every change in the future, as we should probably check if the examples still work if we change a package! Reduces the scope of our local github action to just handle setting up node and pnpm which is needed by every workflow. `lint` and `test` are now specified explicitly in workflows that should run them. We don't need to run those steps when we're doing browser testing. - Vanilla JS examples are not currently tested as they fail to build storacha/w3ui#243 - we can fix in a separate PR. - We need a mechanism to be able to register a space from browser, or add pre-registered test account fixture - storacha/w3ui#244 - We are missing a `multi-file-upload` example - storacha/w3ui#245 <img width="707" alt="Screenshot 2023-01-12 at 02 03 41" src="https://user-images.githubusercontent.com/58871/211958353-b4a587a7-ead7-4957-b028-45b17c41f9a3.png"> <img width="1582" alt="Screenshot 2023-01-12 at 01 57 39" src="https://user-images.githubusercontent.com/58871/211957738-0bfad4e5-a0e4-4ba6-8a13-ee05602f3adc.png"> **whoo!** <img width="871" alt="Screenshot 2023-01-12 at 11 00 28" src="https://user-images.githubusercontent.com/58871/212049726-68f86951-c244-4ed3-bde9-4ca3bfaa25ca.png"> License: MIT Signed-off-by: Oli Evans <[email protected]> Signed-off-by: Oli Evans <[email protected]>
Peeja
pushed a commit
to storacha/upload-service
that referenced
this pull request
Jan 29, 2025
Pulls example tests out to own dir so we can run the same test for each ui library! fixes: storacha#222 You can see it run in CI at https://github.com/web3-storage/w3ui/actions/runs/3901558574/jobs/6663550379#step:6:13 and you can try it out locally from this branch by running: ``` $ pnpm install # one time download of test browsers $ pnpx playwright install # fails for vanilla currently, but is ok, proceed. $ pnpm build:examples $ pnpm test:examples Scope: 20 of 33 workspace projects examples/test/playwright test$ playwright test [30 lines collapsed] │ [30/33] [webkit] › sign-up-in.spec.ts:4:3 › vue: sign in │ [31/33] [webkit] › uploads-list.spec.ts:4:3 › react: uploads list │ [32/33] [webkit] › uploads-list.spec.ts:4:3 › solid: uploads list │ [33/33] [webkit] › uploads-list.spec.ts:4:3 › vue: uploads list │ │ 33 passed (7s) │ To open last HTML report run: │ │ npx playwright show-report │ └─ Done in 7.6s ``` _note: the build fails currently as our vanilla examples fail to build currently, which is why we need these tests!_ Adds and updates run scripts to make it easy to run package or example tests. Most of the time we'd want to run package tests locally, so this is set as the default. ```bash # runs package tests $ pnpm test # builkd examples. must be run before test so the dist dir exits for each $ pnpm build:examples # run example test $ pnpm test:examples # serve examples, so you can poke around as a dev. $ pnpm serve:examples ``` Updates examples to produce relative URLs by setting `base: ''` in vite config. This allows us to serve all the examples from a single static server in the `examples` dir, and `serve` is added with a `serve.json` config to rewrite the paths so the `dist` dir is served for each example. Adds playwright config to fire up the example server Adds github workflow to set up and run the browser tests only if we make a change to the examples. We may change this to run for every change in the future, as we should probably check if the examples still work if we change a package! Reduces the scope of our local github action to just handle setting up node and pnpm which is needed by every workflow. `lint` and `test` are now specified explicitly in workflows that should run them. We don't need to run those steps when we're doing browser testing. - Vanilla JS examples are not currently tested as they fail to build storacha/w3ui#243 - we can fix in a separate PR. - We need a mechanism to be able to register a space from browser, or add pre-registered test account fixture - storacha/w3ui#244 - We are missing a `multi-file-upload` example - storacha/w3ui#245 <img width="707" alt="Screenshot 2023-01-12 at 02 03 41" src="https://user-images.githubusercontent.com/58871/211958353-b4a587a7-ead7-4957-b028-45b17c41f9a3.png"> <img width="1582" alt="Screenshot 2023-01-12 at 01 57 39" src="https://user-images.githubusercontent.com/58871/211957738-0bfad4e5-a0e4-4ba6-8a13-ee05602f3adc.png"> **whoo!** <img width="871" alt="Screenshot 2023-01-12 at 11 00 28" src="https://user-images.githubusercontent.com/58871/212049726-68f86951-c244-4ed3-bde9-4ca3bfaa25ca.png"> License: MIT Signed-off-by: Oli Evans <[email protected]> Signed-off-by: Oli Evans <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.