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

Decouple near-primitives. #5

Open
1 of 4 tasks
akorchyn opened this issue Oct 17, 2024 · 2 comments
Open
1 of 4 tasks

Decouple near-primitives. #5

akorchyn opened this issue Oct 17, 2024 · 2 comments

Comments

@akorchyn
Copy link
Collaborator

akorchyn commented Oct 17, 2024 •
edited
Loading

Currently, developing an app requires near-primitives to interact with the result types of transactions as near-api propagates them.

As for me, it's pretty inconvenient, and would be better if we created some own wrapper type as near-workspaces does

Tasks
Preview Give feedback
@akorchyn akorchyn changed the title Proper transaction result type Transaction result wrapper Oct 17, 2024
@akorchyn akorchyn changed the title Transaction result wrapper Decouple near-primitives. Oct 29, 2024
@akorchyn
Copy link
Collaborator Author

I updated the issue as we have a lot of types coming from near-primitives when querying the chain.
It's mandatory to replace them with our types and not export them to have a more robust API overall.

The motivation is simple. We don't want to have a breaking release on each near-primitives release as it's not that convenient to use. To have that, near-api should have all the parts wrapped :)

@akorchyn
Copy link
Collaborator Author

The work on it will be done in own-types branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@akorchyn