List view
- No due date•0/1 issues closed
- No due date•5/8 issues closed
A group for all of the work related to deprecating freighter-backend v1 and using only v2.
No due date•0/1 issues closedWork related to adding support for SEP-50 and Litemint NFTs in Freighter new collectibles tab and other workflows.
Overdue by 3 month(s)•Due by August 31, 2025•1/4 issues closedRefactor 3 classes of tech debt that have been identified to impact our UX and DX in Freighter. Data fetching - Remove critical data fetching workflows from shared stores in order to better take control of data and it's lifecycles in views that require the data. The current implementation reuses store data thunks and lifecycles across views and routes which results in the "glitchy" loading UX and messy view layer logic related to loading and error states from data fetching. Refactoring routing - Refactor routes that should not be standalone routes. Today several intermediary steps in workflows like send/swap have their own top level URL routes, which means they can be broken by end users reloading pages or otherwise taking steps that don't result in the correct state being setup for the route. We should refactor flows that can be broken by URL manipulation into sub steps of 1 top level route. This change will better represent the relationship between the workflows steps and prevent users from navigating to invalid route that break Freighter. Strengthen critical types and refactor/add error states - Today our typing between critical application boundaries is loose. This makes it hard for our message passing to defensive against invalid messages at the type level. We should tighten our API level types between the background and popup to ensure type level correctness and prevent bad message bugs. We should also tighten our internal API types to ensure they return hard types instead of `any`s which many internal types return today due to the fallback logic which initializes all return values as `any`. We should refactor errors to not expose implementation details or stack traces to end users. We can display end user friendly messages while logging the stack traces for us. We should also ensure all critical error states lead to either a gracefully degraded experience or an explicit error state.
Overdue by 6 month(s)•Due by May 9, 2025•5/7 issues closed- No due date•1/1 issues closed
- No due date•1/1 issues closed
- No due date•21/21 issues closed
There are a variety of things we can do to improve the experience of new contributors to the project. From CICD improvements, to documentation, to code refactoring. This milestone encapsulates all issues that improve the contributor's experience, with the goal of accelerating onboarding and team throughput.
No due date•6/12 issues closed