Voting: app paths

[bpierre]

Requires aragon/aragon.js#405

[coveralls]

Coverage decreased (-0.05%) to 97.816% when pulling 3a0afed on paths-voting into 38a651a on master.

[coveralls]

Coverage increased (+0.01%) to 97.875% when pulling 3944845 on paths-voting into 38a651a on master.

[sohkai]

🙌Amazing, this works really well!

Right now we still have to wait until the vote's been synced from events for the app to load the details page, but we can make it instant later with aragon/client#1163.

[sohkai]

Thoughts on rolling up the path check directly into voteIdFromPath()?

[bpierre]

That’s better yes!

[rperez89]

@sohkai @bpierre Hey guys awesome work! do you have somewhere explained how this work? or maybe how can i see it working on rinkeby?

[sohkai]

It is working on both mainnet and rinkeby, for example at https://rinkeby.aragon.org/#/ngo/0xc3e8deb4a85718388628b9b5758d1fb242a4d0c1/vote/1/

The API documentation is available:

• path: https://hack.aragon.org/docs/api-js-ref-api#path
• requestPath: https://hack.aragon.org/docs/api-js-ref-api#requestpath

Basically, use path to know what route your app should be on at a given time (similar to controlling your routing by parsing URL parameters). Use requestPath() to change the route. The client only rejects path requests if they've come from an unloaded app (to avoid security issues via one app controlling the routes of another app).