Currently 2 of our FE/Routes disable the user from being able to change parameters:
proposal/update - FE/BE Do not enable user to change "Earmark"
There are nuances to both updates (Requested Earmark vs. Selected Earmark) and needs us to pay close attention when making the update.
Other changes (enabling projects to change Project Name) are much more complicated because of our integration/dependency inside of Airtable. For these updates, we need to migrate from Airtable->Mongo, before considering them.
Example: Update Project Name
DoD:
[x] Proposals can change their earmark
[x] When proposal updates, if they change the wallet, we should verify that it has 500 Ocean on there
Problem:
Currently 2 of our FE/Routes disable the user from being able to change parameters: proposal/update - FE/BE Do not enable user to change "Earmark"
There are nuances to both updates (Requested Earmark vs. Selected Earmark) and needs us to pay close attention when making the update.
Other changes (enabling projects to change Project Name) are much more complicated because of our integration/dependency inside of Airtable. For these updates, we need to migrate from Airtable->Mongo, before considering them. Example: Update Project Name
DoD: