Skip to content
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

docs(examples): add workshop 2022-11-14 examples #2204

Merged
merged 1 commit into from
Jan 27, 2023

Conversation

RafaelAPB
Copy link
Contributor

@RafaelAPB RafaelAPB commented Nov 14, 2022

Simple examples using Cacti tailored for the workshop.

Thanks to @AndreAugusto11 and Monica Gomez monicasrgomez@gmail.com @msrgomez for the amazing work.

Works with version 1.0.0 of cactus-tooling.

Depends on #2213
Depends on #2223

@RafaelAPB RafaelAPB force-pushed the workshop-examples branch 3 times, most recently from c220118 to 3ba2ff4 Compare November 14, 2022 15:27
yarn.lock Outdated Show resolved Hide resolved
examples/cactus-workshop-examples/package.json Outdated Show resolved Hide resolved
examples/cactus-workshop-examples/package.json Outdated Show resolved Hide resolved
examples/cactus-workshop-examples/package.json Outdated Show resolved Hide resolved
examples/cactus-workshop-examples/package.json Outdated Show resolved Hide resolved
examples/cactus-workshop-examples/package.json Outdated Show resolved Hide resolved
@takeutak
Copy link
Contributor

takeutak commented Nov 21, 2022

@RafaelAPB Thanks for your contribution and hard work to develop a workshop example!
As Peter suggested, the directory name (cactus-workshop-example) should be changed to some identified name such as cactus-workshop-examples-2022-11-14 because there will be another workshop example in the future.

(@petermetz BTW, the prefix "cactus-" will be changed to cacti- in the future, is it right?)

@RafaelAPB
Copy link
Contributor Author

@petermetz and @takeutak, the updates you recommended have been incorporated

@RafaelAPB RafaelAPB requested review from petermetz and removed request for sandeepnRES, jagpreetsinghsasan, takeutak, izuru0 and petermetz November 22, 2022 12:56
Copy link
Contributor

@petermetz petermetz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RafaelAPB Both the description and the package name (and directory name) should be pinned to the actual workshop instance (2022-11-14) so that we can add more of these packages later

  1. Please fix the above request from earlier and
  2. Squash into a single commit
  3. Update the tsconfig.json to match the conventions of the other packages if possible (if not possible for whatever reason, then let's discuss the details)
  4. Mark the issue dependent with the correct syntax both in the PR description and the commit message.
  5. Set the PR title to match the final remaining (one) commit's subject line.
  6. Make sure that the commit subject line is also identifying the workshop instance.
  7. Make sure that the README title is also identifying the workshop instance.

@takeutak
Copy link
Contributor

takeutak commented Nov 23, 2022

@RafaelAPB

@petermetz and @takeutak, the updates you recommended have been incorporated

Thanks! It is no problem for me, but could you revise this pull-request according to Peter's request? After that I will approve it.

@RafaelAPB RafaelAPB force-pushed the workshop-examples branch 2 times, most recently from 664b20a to 05ebc2f Compare November 24, 2022 23:36
@RafaelAPB RafaelAPB changed the title Workshop examples feat(examples): add workshop 2022-11-14 examples Nov 24, 2022
@RafaelAPB
Copy link
Contributor Author

@

@RafaelAPB Both the description and the package name (and directory name) should be pinned to the actual workshop instance (2022-11-14) so that we can add more of these packages later

  1. Please fix the above request from earlier and
  2. Squash into a single commit
  3. Update the tsconfig.json to match the conventions of the other packages if possible (if not possible for whatever reason, then let's discuss the details)
  4. Mark the issue dependent with the correct syntax both in the PR description and the commit message.
  5. Set the PR title to match the final remaining (one) commit's subject line.
  6. Make sure that the commit subject line is also identifying the workshop instance.
  7. Make sure that the README title is also identifying the workshop instance.

@petermetz updated. Not sure about the changes required for steps 3 and 4.

@RafaelAPB RafaelAPB force-pushed the workshop-examples branch 2 times, most recently from 43ce2cd to bd6470c Compare November 29, 2022 18:47
Copy link
Contributor

@jagpreetsinghsasan jagpreetsinghsasan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, its nice to have such simple examples as well, for getting started.

@takeutak
Copy link
Contributor

LGTM, but this pull-request cannot be merged without resolving this change-request from Peter due to GitHub system.

@petermetz If you have some improvement comments, please feel free to share them.

Copy link
Contributor

@petermetz petermetz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but will mark it with a change request so that we know that it has to be updated after v1.1.3 comes out (which is dropping soon)

@github-actions github-actions bot removed the dependent label Dec 9, 2022
@github-actions
Copy link

github-actions bot commented Dec 9, 2022

@RafaelAPB RafaelAPB requested review from petermetz and removed request for izuru0, sandeepnRES and VRamakrishna December 13, 2022 18:39
Copy link
Contributor

@petermetz petermetz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RafaelAPB Please update to v1.1.3 and then if you run yarn it should disappear the unnecessary diff from the lock file.

Copy link
Contributor

@petermetz petermetz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RafaelAPB You don't appear to have ran yarn to make the lock file changes necessary.

@RafaelAPB
Copy link
Contributor Author

@RafaelAPB You don't appear to have ran yarn to make the lock file changes necessary.

should be good to go now! Thanks for the patience

Copy link
Contributor

@petermetz petermetz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RafaelAPB No worries and thanks for the updates, LGTM.

Simple examples using Cacti tailored for the workshop 2022-11-14.

Thanks to @AndreAugusto11 and
Monica Gomez monicasrgomez@gmail.com @msrgomez for the amazing work.

Works with version 1.0.0 of cactus-tooling.

Depends on hyperledger-cacti#2213

Signed-off-by: André Augusto <andre.augusto@tecnico.ulisboa.pt>
Signed-off-by: Rafael Belchior <rafael.belchior@tecnico.ulisboa.pt>
Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>

Co-Authored-By: Monica Gomez <monicasrgomez@gmail.com>
Co-Authored-By: André Augusto <andre.augusto@tecnico.ulisboa.pt>
Co-Authored-By: Peter Somogyvari <peter.somogyvari@accenture.com>
Signed-off-by: Rafael Belchior <rafael.belchior@tecnico.ulisboa.pt>
@petermetz petermetz merged commit b33ab1b into hyperledger-cacti:main Jan 27, 2023
@RafaelAPB RafaelAPB deleted the workshop-examples branch January 30, 2024 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants