-
Notifications
You must be signed in to change notification settings - Fork 12
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: test todo action #123
Merged
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
namhoang1604
added a commit
that referenced
this pull request
Jul 6, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [x] π Feature - [ ] π Bug Fix - [x] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [x] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> - Implement the vc-api for the holder and verifier. - Implement the open api validator for the vc api router ```yaml # API base path - - $require: '@vckit/vc-api?t=function#HolderRouter' - - $require: '@vckit/vc-api?t=function#IssuerRouter' $args: - createCredential: createVerifiableCredential updateCredentialStatus: updateVerifiableCredentialStatus - - $require: '@vckit/vc-api?t=function#VerifierRouter' $args: - verifyCredential: verifyCredential verifyPresentation: verifyPresentation # VC API docs path - - /vc-api.json - $require: '@vckit/vc-api?t=function#VCApiSchemaRouter' $args: - basePath: :3332 - - /vc-api-docs - $require: '@vckit/vc-api?t=function#VCApiDocsRouter' ``` ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> #100 #92 #115 ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> <img width="1510" alt="image" src="https://github.com/uncefact/project-vckit/assets/13606809/5168be6a-ae27-4b6c-b4d4-7b51d8175d27"> <img width="536" alt="image" src="https://github.com/uncefact/project-vckit/assets/13606809/1a1d08e8-fc02-48f5-aced-1ec56a2c24b5"> <img width="426" alt="image" src="https://github.com/uncefact/project-vckit/assets/13606809/181eac6d-0998-4f31-9686-d855c2c6e626"> ## Added tests? - [x] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [x] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
to namhoang1604/project-vckit
that referenced
this pull request
Jul 6, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [x] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> Update the configuration for the unit test to make it can run at the root. the vckit-oa-renderers package will run the test script separately with another and include that script to the main test script `pnpm test` to run at the root. ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes uncefact#123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [x] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Jul 6, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [x] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> The JSON-LD lib expanded the vc with the wrong data of `@id` of renderMethod object. Eg: ``` # The **@id** value before expanding <div style=\"width:300px; height:100px; border: 2px solid black; text-align:center\">ABC</div> # The **@id** value after expanding 300px; height:100px; border: 2px solid black; text-align:center\">ABC</div> ``` ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [x] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
to namhoang1604/project-vckit
that referenced
this pull request
Jul 29, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [x] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> Update the configuration for the unit test to make it can run at the root. the vckit-oa-renderers package will run the test script separately with another and include that script to the main test script `pnpm test` to run at the root. ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes uncefact#123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [x] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Aug 7, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [x] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Aug 7, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [x] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> The encrypted storage plugin encrypts the vc when issue, which uses the middleware to intercept the issue api response. The response will return the key, id, and vc, based on that can decrypt the encrypted vc which is fetched from the API `/encrypted-storage/encrypted-data/:id` ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [x] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Aug 7, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [x] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> Implement the react component that includes the QR code component and the document wrapper includes the QR code component. Both components are used to render the verifiable credential/verifiable presentation have the renderer method to attach the QRcode on the rendered document. ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> <img width="1512" alt="image" src="https://github.com/uncefact/project-vckit/assets/13606809/c592a392-9807-45fe-b347-ca1838503cb7"> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [x] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [x] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Aug 7, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [x] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> Credential status plugin for the [revocation list 2020](https://w3c-ccg.github.io/vc-status-rl-2020/) ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [x] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com> Co-authored-by: Hoa Ngo <hoa.ngo@gosource.com.au>
namhoang1604
added a commit
that referenced
this pull request
Aug 7, 2023
β¦ugins (#138) <!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com> Co-authored-by: Hoa Ngo <hoa.ngo@gosource.com.au>
namhoang1604
added a commit
that referenced
this pull request
Aug 9, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [x] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> Implement the credential router which is used to navigate the issuing and verifying request rely on the proof format of the credential ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [x] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Aug 9, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [x] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Aug 9, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [x] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [x] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid -->
namhoang1604
added a commit
that referenced
this pull request
Aug 11, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [x] π Documentation Update - [ ] π¨ Style - [x] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [x] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Aug 14, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [x] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR update the node and pnpm version. ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> #143 ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Aug 14, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [x] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. This PR update the instruction on Readme --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Aug 17, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [x] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> - Fix missing the additional fields from schema when issue the vc - Fix storing the encrypted data when issue - Fix retrieving the proofFormat when issue ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Aug 18, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [x] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
pushed a commit
that referenced
this pull request
Aug 18, 2023
β¦to cmpile the package (#150) <!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [x] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> Co-authored-by: Zach Zeus <zachary@bizcubed.com.au>
namhoang1604
added a commit
that referenced
this pull request
Aug 18, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [x] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR refactor the revocation list 2020 package to make that suitable with the database providers to lock the change on the revocation list and data. ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
pushed a commit
that referenced
this pull request
Aug 18, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [x] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [x] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid -->
namhoang1604
pushed a commit
that referenced
this pull request
Aug 21, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [x] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [x] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid -->
namhoang1604
added a commit
that referenced
this pull request
Sep 5, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [x] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR adds the CICD scripts ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
to gs-gs/project-vckit
that referenced
this pull request
Sep 6, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> - [ ] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [x] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR adds the CICD scripts <!-- Please use this format link issue numbers: Fixes uncefact#123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> <!-- Visual changes require screenshots --> - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Sep 7, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [x] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> - Fix migration script to ignore when the table is existing - Rename active button to unrevoke - Comment the did ethr in default config ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [x] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Sep 16, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [x] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR fixes the wrong configuration for the CD script ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [x] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com> Co-authored-by: Kseniya Shychko <k.shychko@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Oct 11, 2023
β¦ext (#156) <!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [x] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [x] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Co-authored-by: Hoa Ngo <hoa.ngo@gosource.com.au>
namhoang1604
added a commit
that referenced
this pull request
Dec 26, 2023
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [x] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR implements a plugin credential merkl disclosure proof that integrates to the credential router to issue and verify via the credential router plugin. ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [x] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [x] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Jan 9, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [x] π CI - [x] π¦ Chore (Upgrade) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR upgrade the dependencies ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
pushed a commit
that referenced
this pull request
May 22, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [x] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> CI CD: [#458](gs-gs/fa-ag-trace#458) ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> **Configure the pipeline to fail if the code coverage falls below the specified threshold** <img width="1039" alt="image" src="https://github.com/uncefact/project-vckit/assets/59736798/45df4eba-6a0b-42e4-894d-7707c34d4862"> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [x] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid -->
namhoang1604
pushed a commit
that referenced
this pull request
May 28, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [x] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [x] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid -->
namhoang1604
added a commit
that referenced
this pull request
May 28, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [x] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com> Co-authored-by: Huy Nguyen <huy.nguyenkim.h@gmail.com>
namhoang1604
pushed a commit
that referenced
this pull request
May 31, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [x] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [x] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid -->
namhoang1604
added a commit
that referenced
this pull request
Jun 5, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [x] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [x] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR updates the default agent configuration ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> gs-gs/fa-ag-trace#475 gs-gs/fa-ag-trace#478 ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [x] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
pushed a commit
that referenced
this pull request
Jun 5, 2024
β¦t variable setup (#188) <!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [x] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description [490](gs-gs/fa-ag-trace#490 )<!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [x] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid -->
ldhyen99
added a commit
that referenced
this pull request
Jun 5, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [x] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description [488](gs-gs/fa-ag-trace#488) <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [x] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid -->
namhoang1604
added a commit
that referenced
this pull request
Jun 7, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [x] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> Resolves gs-gs/fa-ag-trace#477, resolves gs-gs/fa-ag-trace#491, resolves gs-gs/fa-ag-trace#473, resolves gs-gs/fa-ag-trace#479, resolves gs-gs/fa-ag-trace#490 ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [x] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Jun 7, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [x] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR fixes the bug for bitstring status on explorer to switch to use revocation list status ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> Fixes gs-gs/fa-ag-trace#492 ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Jun 7, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [x] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR add warning for install pnpm ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> Resolves gs-gs/fa-ag-trace#493 ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
pushed a commit
that referenced
this pull request
Jun 12, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [x] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [x] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [x] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid -->
namhoang1604
pushed a commit
that referenced
this pull request
Jun 13, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [x] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> Docs: gs-gs/fa-ag-trace#498 ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [x] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid -->
namhoang1604
added a commit
that referenced
this pull request
Jun 14, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [x] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR adds documentation site for VCKit ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [x] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com> Co-authored-by: ducpm511 <117595496+ducpm511@users.noreply.github.com> Co-authored-by: Yen Le Diep Hoang <59736798+ldhyen99@users.noreply.github.com> Co-authored-by: Huy Nguyen <huy.nguyenkim.h@gmail.com>
namhoang1604
pushed a commit
that referenced
this pull request
Jun 14, 2024
β¦ls (#197) <!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [x] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description I found something regarding this issue. If you want to know more, please read the comment in the attached ticket below.<!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> gs-gs/fa-ag-trace#476 ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> <img width="1440" alt="image" src="https://github.com/uncefact/project-vckit/assets/59736798/8219d4ff-d902-4119-8c9d-cb43c108a668"> <img width="1440" alt="image" src="https://github.com/uncefact/project-vckit/assets/59736798/405d4881-9f39-4452-adb1-f92c40c3f3eb"> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [x] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid -->
namhoang1604
pushed a commit
that referenced
this pull request
Jul 30, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [x] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid -->
namhoang1604
added a commit
that referenced
this pull request
Sep 13, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [x] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description **Note**: - The DID Documents when configured JsonWebKey will contain two types: JsonWebKey and JsonWebKey2020. The JsonWebKey2020 for purposing issue Bit String Status - Many Veramo libraries need to be re-installed using our custom Veramo because these libraries install each other. - Only support DID web and Bit String Status list **Setup**: - Please run `pnpm build-clean` before start - In `postinstall` of `package.json` file, change to `git pull --depth=1 origin feat/enveloping_proof` - Run `pnpm install` & `pnpm run build` & `pnpm vckit config` **Step for testing Enveloping proof:** - Config in VCKit: 1. In agent.yml, change DID Documents: ```yml - - $require: '@vckit/remote-server?t=function#WebDidDocRouter' $args: - keyMapping: Ed25519: JsonWebKey ``` - In api-docs 1. Creates and returns a new identifier 2. Create the bit string status, example payload: ```json { "statusPurpose": "revocation", "bitStringLength": 10, "bitstringStatusIssuer": "did:web:example", "statusSize": 10, } ``` 3. Issue a credential with the status and the issuer created, for example payload: ```json { "credential": { "@context": [ "https://www.w3.org/ns/credentials/v2", "https://www.w3.org/ns/credentials/examples/v2" ], "id": "http://university.example/credentials/1872", "type": [ "VerifiableCredential", "ExampleAlumniCredential" ], "issuer": "did:web:new_identifier", "validFrom": "2010-01-01T19:23:24Z", "credentialSchema": { "id": "https://example.org/examples/degree.json", "type": "JsonSchema" }, "credentialSubject": { "id": "did:example:123", "degree": { "type": "BachelorDegree", "name": "Bachelor of Science and Arts" } }, "credentialStatus": [{ "id": "http://localhost:3332/credentials/status/bitstring-status-list/5#0", "type": "BitstringStatusListEntry", "statusPurpose": "revocation", "statusListIndex": "10", "statusListCredential": "http://localhost:3332/credentials/status/bitstring-status-list/5" }] }, "options": { "created": "string", "challenge": "string", "domain": "string", "credentialStatus": { "type": "string" }, "proofFormat":"EnvelopingProofJose" } } ``` 4. Verify this Enveloping Proof VC 5. Revoke credential status and test again to make sure VC is revoked <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> <img width="583" alt="image" src="https://github.com/user-attachments/assets/a10b5983-b6dc-4622-84c9-afaa622304b9"> ## Added tests? - [x] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [x] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Co-authored-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Sep 19, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [x] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [x] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR adjusts the workflows to allow manually trigger and update the dockerfile ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Sep 24, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [x] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR fixes the bitstring status list data model that is facing the problem when running the vckit with postgres ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid -->
namhoang1604
added a commit
that referenced
this pull request
Sep 24, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [x] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR adds the authentication using API key for the APIs of vc-api plugin ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> gs-gs/fa-ag-trace#621 ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Sep 27, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [x] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR enhances the bitstring status list to use the enveloping proof for issuing ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
pushed a commit
that referenced
this pull request
Oct 1, 2024
β¦218) <!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [x] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> <img width="878" alt="image" src="https://github.com/user-attachments/assets/c1ccdf6e-4820-47c2-a471-c76f8f642c11"> <img width="880" alt="image" src="https://github.com/user-attachments/assets/e754112c-80ff-4458-bcb3-ebcfee91573f"> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid -->
namhoang1604
added a commit
that referenced
this pull request
Oct 3, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [x] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR fixes the issue when setting status for bitstring status list credential. It was missing the set status function when integrated with the enveloping proof. ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Oct 7, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [x] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR refactors the VC-api to comply the VC-api test suite ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com> Co-authored-by: Huy Nguyen <huy.nguyenkim.h@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Oct 15, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [x] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [x] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Co-authored-by: Nam Hoang <hoangxuannam160493@gmail.com>
ldhyen99
added a commit
that referenced
this pull request
Nov 20, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [x] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [x] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid -->
ldhyen99
added a commit
that referenced
this pull request
Dec 3, 2024
β¦tion key <!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [x] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> #227 ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [x] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid -->
namhoang1604
added a commit
that referenced
this pull request
Dec 6, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [ ] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [x] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR adds the job to build the document for the build and test workflow that will be triggered when the PR is created ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> Closes #232 gs-gs/fa-ag-trace#795 ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [ ] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
ldhyen99
added a commit
that referenced
this pull request
Dec 24, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [x] π Feature - [ ] π Bug Fix - [x] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [x] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid -->
namhoang1604
added a commit
that referenced
this pull request
Dec 24, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [x] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR exposes the new API router to support customize and versioning for API swagger. ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> gs-gs/fa-ag-trace#865 ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
namhoang1604
added a commit
that referenced
this pull request
Dec 27, 2024
<!-- For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. For a timely review/response, please avoid force-pushing additional commits if your PR already received reviews or comments. Before submitting a Pull Request, please ensure you've done the following: - π Read the [Contributing Guide](https://github.com/uncefact/project-vckit/blob/main/CONTRIBUTING.md). - π Read the [Code of Conduct](https://github.com/uncefact/project-vckit/blob/main/CODE_OF_CONDUCT.md). - π·ββοΈ Create small PRs. In most cases, this will be possible. - β Provide tests for your changes. - π Use descriptive commit messages following [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). - π Update any related documentation and include any relevant screenshots. --> ## What type of PR is this? (check all applicable) - [x] π Feature - [ ] π Bug Fix - [ ] π Documentation Update - [ ] π¨ Style - [ ] π§βπ» Code Refactor - [ ] π₯ Performance Improvements - [ ] β Test - [ ] π€ Build - [ ] π CI - [ ] π¦ Chore (Release) - [ ] β© Revert ## Description <!-- Please do not leave this blank This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. --> This PR adds Swagger API for the new exposed API route, the API also supports versioning. ## Related Tickets & Documents <!-- Please use this format link issue numbers: Fixes #123 https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> gs-gs/fa-ag-trace#867 gs-gs/fa-ag-trace#866 ## Mobile & Desktop Screenshots/Recordings <!-- Visual changes require screenshots --> <img width="1499" alt="image" src="https://github.com/user-attachments/assets/a5ac8726-ecb5-4b6d-a96b-3198204fd758" /> <img width="893" alt="image" src="https://github.com/user-attachments/assets/0aa7c9cb-ed44-45c3-aa5b-06969686a0be" /> <img width="777" alt="image" src="https://github.com/user-attachments/assets/b13a1abe-ed0c-4789-82c6-6999daf25676" /> ## Added tests? - [ ] π yes - [x] π no, because they aren't needed - [ ] π no, because I need help ## Added to documentation? - [ ] π README.md - [ ] π [vc-kit doc site](https://uncefact.github.io/vckit/) - [ ] π storybook - [ ] π no documentation needed ## [optional] Are there any post-deployment tasks we need to perform? <!-- note: PRs with deleted sections will be marked invalid --> --------- Signed-off-by: Nam Hoang <hoangxuannam160493@gmail.com>
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.
What type of PR is this? (check all applicable)
Description
Related Tickets & Documents
Mobile & Desktop Screenshots/Recordings
Added tests?
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?