You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A tricky part of freighter-api development is that you can't always predict what version of the extension the user has. Not only does freighter-api itself need to be backwards compatible, it needs to be backwards compatible with the extension. It can be a tricky thing to get right and involves a lot of manually testing different versions of the codebase. Is there a way to automate this?
We would need to spin up an environment with a web app that can install different versions of freighter-api from npm and run through each method
We would also need to install the current version of Freighter plus the next version of Freighter to make sure all methods are working with the versions of Freighter that are likely to be in the wild
The text was updated successfully, but these errors were encountered:
A tricky part of freighter-api development is that you can't always predict what version of the extension the user has. Not only does freighter-api itself need to be backwards compatible, it needs to be backwards compatible with the extension. It can be a tricky thing to get right and involves a lot of manually testing different versions of the codebase. Is there a way to automate this?
The text was updated successfully, but these errors were encountered: