You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Check Figma for the UI reference of CrowdAction Info, Images, Assign Commitments and Assigned Commitments
Architecture
To separate and encapsulate the logic of the form, One approach is to create a bloc for each section and a "high order bloc" that is going to be subscribed to all the other blocs. So everytime there is a state change in one of the "sub-blocs", it going to trigger a state update in the main bloc.
Could be blocs or cubits depending on the situation.
Provisional steps to tackle this issue:
Check Figma for the UI reference of CrowdAction Info, Images, Assign Commitments and Assigned Commitments
Architecture
To separate and encapsulate the logic of the form, One approach is to create a bloc for each section and a "high order bloc" that is going to be subscribed to all the other blocs. So everytime there is a state change in one of the "sub-blocs", it going to trigger a state update in the main bloc.
Could be blocs or cubits depending on the situation.
Subtasks
GET
request to fetch the template commitments #29The text was updated successfully, but these errors were encountered: