Integrate deep linking in the Projects app

[stellarmagnet]

We should implement deep links for the following pages:

• Project detail page
• Review application panel (per applicant)
• Review work panel (per submission)
• Issues landing page (all projects shown)
  • Note: eventually we should be able to link a specific filter set
• Settings tab

Reference implementations

• Voting: app paths aragon/aragon-apps#1029
• Custom app paths aragon/client#846

[stellarmagnet]

@ottodevs @topocount , what changes need to be made to the Projects contract to be able to display the deep link in the radspec, specifically for the "review submission" part of the flow? E.g. the link is to the work submission of a particular user. Do we need the radspec IPFS helper to be able to somehow determine the deep link based on the IPFS hash?

LOC:

open-enterprise/apps/projects/contracts/Projects.sol

Line 473 in 6f1612d

* @notice `_approved ? 'Accept' : 'Reject'` work for issue `_issueNumber` with info: `_updatedSubmissionHash`

[ottodevs]

@ottodevs @topocount , what changes need to be made to the Projects contract to be able to display the deep link in the radspec, specifically for the "review submission" part of the flow? E.g. the link is to the work submission of a particular user. Do we need the radspec IPFS helper to be able to somehow determine the deep link based on the IPFS hash?

LOC:

open-enterprise/apps/projects/contracts/Projects.sol

Line 473 in 6f1612d

* @notice `_approved ? 'Accept' : 'Reject'` work for issue `_issueNumber` with info: `_updatedSubmissionHash`

The way you seem to propose, I guess the radspec IPFS helper would be needed to decode the issueId from it, because the deep-link is based on the issueId.

The alternative approach would be start using the internal github issue numbers, that are already unique, I recently discovered about this approach and it would be really interesting to start using this, since you can decode the internal issue number from the issue id and the other way around... So the change would be start encoding the github issue number into the contract, that way we would not need to use the radspec IPFS helper for this case.

[javieralaves]

@ottodevs I notice this issue is connected to a merged PR. Are there any more changes needed before we move this to Review?

[javieralaves]

Testing this in the continuous deploy DAO on December 20th 2019, everything works as expected!