-
Notifications
You must be signed in to change notification settings - Fork 97
Create 2018-12-12--gui-and-in-web-browsers-weekly.md #805
Conversation
- Next: | ||
- 2 more usability testing session for webui. write up the common issues. Propose next round of improvements to webui | ||
- Refactoring to webui and ipfs-redux-bundle to work with the api changes in ipfs-http-client \*\*help wanted\*\* | ||
- Refactoring ipld-explorer-components to work with changes to dag-pb and ipld apis. \*\*help wanted\*\* (good opportunity to pair on ipld-explorer code.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll be available on Monday and Tuesday to help with this - updated WebUI blocks JS IPFS 0.34 release right now and I wanted it to happen this year.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know @olizilla wants to do some bigger refactoring, though there's also ipfs/ipld-explorer-components#6 which made things work for the dag-cbor API change (at least AFAICT).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
of note, Web UI is using older versions of js-ipld and js-ipfs-api (the lib formally known as). Right now, as long as I don't upgrade ipld, Web UI still works as intended, which is what I'd expect. I will need to upgrade the ipld explrorer UI when I take the new ipld lib, but I expect it to keep working until i do.
Same goes for the file api from js-ipfs. I'd assume that older clients would still be able to access the http api in the same way, and new clients would use the new way. Or is this a breaking change to the http api too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's no (intended) breaking change to the HTTP API.
To be honest, I used it on the DHT branch and got a blank page for the files page...I didn't look into it any further at the time, so it just needs some investigation. I initially thought it was because of the breaking core API changes but as @olizilla pointed out the WebUI is bundled with it's dependencies, so should still work (since there's no HTTP API breaks).
- I was blocked by laryngitis. I’,m on the mend now. | ||
- Next: | ||
- 2 more usability testing session for webui. write up the common issues. Propose next round of improvements to webui | ||
- Refactoring to webui and ipfs-redux-bundle to work with the api changes in ipfs-http-client \*\*help wanted\*\* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll tackle this one.
cc #790