Vue route/component(s) for Listing

[robrobbins]

Re #5 bullet 1

It is irrelevant that .../new may redirect to here. We may choose to not do that...

anyway

see #10 pertaining to listing vs candidate

If it is decided that .../listing/hash shows the candidate (the listing as candidate:true or something).

@thirtyaughtsix in my opinion this "page" is where the dapp can query for the state of the listing/candidate in question. There are a couple of ways to do this

• simply ask if the given hash is a listing. we know this will be false until it is voted in.
• the same can be asked if this hash is a candidate. again see Vue route/component(s) for candidate #10
• in Protocol: Listing -> new #9 the client will recieve back a transactionHash this could be kept and then used to query the blockchain with. If this is the case, more questions arise about the keeping of these beyond the page lifecycle

[robrobbins]

@thirtyaughtsix @MelvinMallari I'd say this is the ticket to create the .../listing/hash route that shows the listing | candidate.

up to you if you want to combine route/business-logic/ui/ux or split into sub-tickets.