Proposal warns - tracking issue

[WRadoslaw]

#2242
Warns to be covered:

• Funding request Funding request proposal #2321 Funding request proposal #2321
• The council budget is no less than the sum of amounts

---

• Create Working Group Lead Opening - Create Working Group Lead Opening: Execution Constraints Validation #2280

---

• Working Group Lead Proposals: cancel opening/ decrease stake/ terminate lead #2323

• Cancel Working Group Lead Opening

• Decrease Working Group Lead Stake

• Terminate Working Group Lead

• Same as when creating an opening for workers in the given group with given inputs, except signer check (?)

---

#2324

• Fill Working Group Lead Opening
• Same as when filling opening in group for worker with given inputs, except application_id as winners and signer check
  ℹ️ See details here> Create Working Group Lead Opening: Execution Constraints Validation #2280

#2325

• Slash working group lead
  Same as when slashing a worker in group with given inputs, except
• signer check,
• worker corresponding to worker_id must be lead

---

#2326

• Set Working Group Lead Reward
• Same as when updating reward of a worker in group with given inputs, except signer check

---

#2327

• Update Working Group Budget
• If budget_update is non-negative, then this it must be no less than the council budget, otherwise the absolute value must be no less than the current group budget.

---

#2328

• Set Membership Lead Invitation Quota
• The membership working group has an assigned lead with membership id membership_id.

┆Issue is synchronized with this Asana task by Unito

[WRadoslaw]

@dmtrjsg

Does that design fulfills the expectations? Ofc message can be adjusted.

[bedeho]

This should not be part of Olympia release, as it is not critical enough to block launch, so removing label.

[dmtrjsg]

@WRadoslaw, comments from @MattAugustynowicz

• Let's replace the icon with an alert from this subpage please, from what I've seen the highlighted messages use outline icons anyway, so we'll remain consistent
  Icon 👉 https://www.figma.com/file/GlgN8uBRtvtMJtiOsdtDF7/Pioneer-Design?node-id=1405:76570

• Let's not use capitals in the word "WARNING". I didn't find this writing structure in the draft, so we'll remain consistent here too. Let's just write "Warning"
• The spacing between the checkbox icon and the text seems to be too large. In the project we have 4px spacing between the 24px icon and the text, so we can use that. But, if you used such checkboxes throughout the project, let's leave it like this 🙂

Copy in the "warning box": "Warning: Proposal parameters provided do not satisfy current runtime execution constraints. If the proposal was executed with the current runtime state, then it would get rejected automatically."

Copy in the "checkbox": "I understand this proposal will fail if execution constraints remain unchanged." Required =true to enable CTA "create proposal

• Move checkbox to the bottom: like here:

[dmtrjsg]

@thesan @WRadoslaw as discussed this morning, it is more about validation on each field. Pls see comment from Bedeho:

What I am saying is that the inputted field values for the proposal parameters (in this case the specific proposal parameters), need to be validated against the execution conditions of the given proposal type, and this will require the validation logic in almost all cases actually fetching certain values from the runtime state. If the conditions are not satisfied, then you should make it hard for the user to proceed inadvertently.
So its really about blocking here, not explaining, people don't want things explained.

[dmtrjsg]

#2305

[dmtrjsg]

Closing this issue in favour of tracking each proposal type (with some exceptions for grouping similar ones) as separate issues, mapped to this (original ticket, which is now converted to epic) - #2328

[dmtrjsg]

Closing this issue in favour of tracking each proposal type (with some exceptions for grouping similar ones) as separate issues, mapped to this (original ticket, which is now converted to epic) - #2328