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.

Sign up for GitHub

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

Jump to bottom

Create an easy way to register trigger using Client #2009

Closed
Arjentix opened this issue Mar 25, 2022 · 1 comment
Closed

Create an easy way to register trigger using Client #2009

Arjentix opened this issue Mar 25, 2022 · 1 comment
Labels
Enhancement New feature or request good first issue Good for newcomers iroha2-dev The re-implementation of a BFT hyperledger in RUST

Comments

@Arjentix
Copy link
Contributor

Most of our downstream clients may want a feature to easy register trigger. So it should be a new method in Client structure. It should be looking something like build_register_tirgger_isi() in client/tests/integration/triggers/*
@Arjentix Arjentix added Enhancement New feature or request good first issue Good for newcomers iroha2-dev The re-implementation of a BFT hyperledger in RUST labels Mar 25, 2022
@Arjentix Arjentix mentioned this issue Mar 25, 2022
Merged
@appetrosyan appetrosyan added Chore This is a small task that can be done at any point in time and is easier than others and removed Chore This is a small task that can be done at any point in time and is easier than others labels Jun 8, 2022
@mversic
Copy link
Contributor

mversic commented Dec 7, 2023

we don't see a proper way to do this atm. The API will often be lacking. This feature will be reconsidered in the future

@mversic mversic closed this as completed Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Enhancement New feature or request good first issue Good for newcomers iroha2-dev The re-implementation of a BFT hyperledger in RUST
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@appetrosyan @Arjentix @mversic