Closed janniks closed 7 months ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
stacksjs-docs | ❌ Failed (Inspect) | Feb 5, 2024 3:40pm |
@janniks So this PR is a small set of changes and is mostly just refactoring with almost no impact for developers right?
Yes mostly small refactoring, however there are breaking changes with many consequences in the chain of PRs. I tried to split them up for easier review and following the refactor. Feel free to take a look at the other PRs mentioned in the description, some will be more breaking than others, but follow the same narrative.
EPIC 🏰 Breaking Refactoring Stacks.js
Goal: Make network/networking more obvious and less confusing for developers. While the default code will stay largely the same for most users, it should become more clear what node URL, and fetch implementation is used when.
fetch
functions from network and introduceStacksNodeApi
, which can derive it's URL from a network, but should be treated separately -- more closely mirroring to what's actually happening in the background. Can be seen as a maintained API client, with post-processing of responses.{ api: { url: "my-node.com" }, ...}
in the params of most relevant tx functions.Supersedes https://github.com/hirosystems/stacks.js/pull/1596
@ Reviewers: ✨ Please feel free to leave any feedback on these PRs. Going over the code will show what it's like to code in the new style. So any ideas and feedback (especially negative) is welcome 🙏
This PR:
next
↑feat/next-cleanup-common-files
this PR 🟢 ↑feat/next-add-new-network
#1623 ↑feat/next-add-api-package
#1624 ↑feat/next-update-api-stacking
#1625 ↑feat/next-update-cli
#1626