@frabrunelle has caught a couple of errors after updating function nomenclature to better match the API docs. I’ll sort these and push a new release this evening, so perhaps better to hold off on moving to 0.2.8 for now.
This weekend back from my tip I’ve been firing into safe-js with documentation and tests. So we’ve now got a fledgling test suit that should provide some stability for the js lib that’ll be powering app interactions in the browser.
safe-js documentation has been added for all 0.5 level APIs, and you can read it over at the repo there. Safe-js has also been updated with the foundations for some 0.6 API with some PRs from @Krishna, and the 0.2.8 version includes these, too.
Please feel free to PR with any improvements to safe-js, code, tests or documentation. Any changes to tested code should be passing those tests now.
Now that there’s a test suite for safe-js implemented, I can refocus on the browser implementations itself. I’ll be looking to:
- Sort appveyor deployments to the same github release as travis (so we only have one link!)
- Update beaker to beaker core latest version (0.3.5 as I write).
- Add toggle for ‘safe’ mode and http request blocking.
- Start browser data storage/sync to the SAFE network.
- Improve safe-js tests and coverage.