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(provider): extend tari universe provider types #48

Merged
merged 3 commits into from
Feb 19, 2025

Conversation

karczuRF
Copy link
Contributor

Description

This PR extends the VauldData type by token_symbol and vault_id. Also removes redundant code from the TariUniverseProvider. Additionally some cleanup.

Motivation and Context

Fix ts type errors while integrating the Ootle into the Tari Universe.

How Has This Been Tested?

Manually.

What process can a PR reviewer use to test or verify this change?

Breaking Changes

  • None
  • Requires data directory on base node to be deleted
  • Requires hard fork
  • Other - Please specify

@sdbondi sdbondi added this pull request to the merge queue Feb 19, 2025
Merged via the queue into tari-project:main with commit cdb7604 Feb 19, 2025
4 checks passed
@karczuRF karczuRF mentioned this pull request Feb 20, 2025
4 tasks
mrnaveira pushed a commit that referenced this pull request Feb 20, 2025
Description
---
Update `tari_provider` and `tari_universe` packages to version 0.4.1
after merge changes from #48

Motivation and Context
---

How Has This Been Tested?
---

What process can a PR reviewer use to test or verify this change?
---

<!-- Checklist -->
<!-- 1. Is the title of your PR in the form that would make nice release
notes? The title, excluding the conventional commit
tag, will be included exactly as is in the CHANGELOG, so please think
about it carefully. -->


Breaking Changes
---

- [x] None
- [ ] Requires data directory on base node to be deleted
- [ ] Requires hard fork
- [ ] Other - Please specify

<!-- Does this include a breaking change? If so, include this line as a
footer -->
<!-- BREAKING CHANGE: Description what the user should do, e.g. delete a
database, resync the chain -->
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.

3 participants