✨ Tobias: Expose Trust#show with link to Payout#new
#23
Conversation
zspencer
force-pushed
the
tobias/issuing-payouts-sprout-tobias-gizmo
branch
from
fd8fcef to
3f75e19
Compare
zspencer
force-pushed
the
tobias/issuing-payouts-sprout-tobias-gizmo
branch
from
3ac7392 to
d0472e3
Compare
zspencer
force-pushed
the
tobias/issuing-payouts
branch
from
6ba9035 to
b1b3055
Compare
zspencer
force-pushed
the
tobias/issuing-payouts-sprout-tobias-gizmo
branch
from
edc30a3 to
3bfafe0
Compare
- #1 - zinc-collective#709 - For a #9 to leverage the behavior we described, we need a way to put tobias on the web. zinc-collective#709 are the equivalent of an "App" in the Convene world. - Note: `Gizmo` and `Furniture` are equivalent. We probably should finish zinc-collective#1472 - The migration change makes sure that ahttps://github.com//issues/4 is connected to #1
Next steps might include: create "New Payout" link Co-Authored-By: Zee <[email protected]> Co-Authored-By: JuanCarlosTC <[email protected]>
Instead, we use the mixin as a kind of "nod-to-the-odd"
This gets us to our next interaction in the system test and prepares to build a form with the fields necessary to issue a Payout.
zspencer
force-pushed
the
tobias/issuing-payouts-sprout-tobias-gizmo
branch
from
a984ff1 to
b7f902b
Compare
zspencer
changed the title
Tobias: Sprout Tobias GizmoTobias: Issue a Payout via the Web
zspencer
changed the title
Tobias: Issue a Payout via the WebTobias: Expose Trust#show with link to Payout#new
|
@chloeinnvaer and/or @JuanCarlosTC - if you get a moment could you read this pull request and leave comments with observations or questions? I don't want to merge until another person has parsed the code a bit. |
| expose :trust, model: Trust | ||
|
|
||
| def show | ||
| authorize trust |
There was a problem hiding this comment.
The authorize method comes from Pundit, and is how we link the code in TrustPolicy, which describes who is allowed to see or change the Trust model, to the action being taken by the user.
| @@ -0,0 +1,11 @@ | |||
| class Tobias | |||
| class Routes | |||
| def self.append_routes(router) | |||
There was a problem hiding this comment.
When we call router.resources, we are connecting the URL path to the application.
/spaces/:space_id/rooms/:room_id, nested under the "Section" the TOBIAS is in.
So, resources :tobiases creates an entry point into our application at the /spaces/:space_id/rooms/:room_id/tobiases path. When we nest resources calls within a do...end block, like we do with router.resources :trusts this nests them within that path , a-la /spaces/:space_id/rooms/:room_id/tobiases/:tobias_id/trusts
What path do you think the line with router.resources :payouts creates?
🌱🗜️✨
TOBIAS: TOpical Basic Income Administration System #1🥔✨
Gizmosconvene#709For a 💰👩🏽💼
Treasurer#9 to issue a 💸Payout#8 from the 💰Trust#4 to a 💪🏽🧑🏽🔧Benificiary#5, we need a human / computer interface to enter the 💸Payout#8.Notes:
GizmoandFurnitureare equivalent. We probably should finish 🧹 Rename fromRoomtoSectionandFurnituretoGizmoconvene#1472The migration change links the dtabase tables for a 💰
Trust#4 and 🌱🗜️✨TOBIAS: TOpical Basic Income Administration System #1