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

fix: Generic promise handling & fixes on private key #173

Merged
merged 3 commits into from
Jan 26, 2023
Merged

Conversation

Eengineer1
Copy link
Contributor

  • Adds on generic type safety.
  • Cleanups.

@Eengineer1 Eengineer1 merged commit cd72355 into develop Jan 26, 2023
@Eengineer1 Eengineer1 deleted the polishes branch January 26, 2023 22:28
cheqd-bot bot pushed a commit that referenced this pull request Jan 26, 2023
## [2.0.0-develop.3](2.0.0-develop.2...2.0.0-develop.3) (2023-01-26)

### Bug Fixes

* Generic promise handling & fixes on private key ([#173](#173)) ([cd72355](cd72355))
@cheqd-bot
Copy link

cheqd-bot bot commented Jan 26, 2023

🎉 This PR is included in version 2.0.0-develop.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

cheqd-bot bot pushed a commit that referenced this pull request Jan 27, 2023
## [2.0.0](1.7.20...2.0.0) (2023-01-27)

### ⚠ BREAKING CHANGES

* On track with v1 on-ledger release (#171)

### Features

* Integrate V2 Protos ([55df78b](55df78b))
* On track with v1 on-ledger release ([#171](#171)) ([675797f](675797f))
* Update import paths ts-proto ([c2353af](c2353af))

### Bug Fixes

* Added ability to read linked resource data from file ([#177](#177)) ([14784e6](14784e6))
* Fixed auto-load on resource & type fixes ([#172](#172)) ([aba5f50](aba5f50))
* Generic promise handling & fixes on private key ([#173](#173)) ([cd72355](cd72355))
* Improved promise handling ([#174](#174)) ([f84a20c](f84a20c))
@cheqd-bot
Copy link

cheqd-bot bot commented Jan 27, 2023

🎉 This PR is included in version 2.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@cheqd-bot cheqd-bot bot added the released label Jan 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

1 participant