🎨 [Frontend] Patch study from Study Editor

[odeimaiz]

What do these changes do?

In order to get rid of the PUT study call, this PR, following this other one, replaces the PUT calls made from the Study Editor with PATCH calls.

For now, until we make sure it works as expected, these patch calls will only be made in the master deployment.

Related issue/s

How to test

Dev-ops checklist

• No ENV changes or I properly updated ENV (read the instruction)

done

[pcrespov]

nice.

From the animationsI noticed that when you add a node, the PATCH request they seem to run in pairs ... they look like duplicated. Is there by any chance this is done accidentally or they have a purpose?

[odeimaiz]

nice.

From the animationsI noticed that when you add a node, the PATCH request they seem to run in pairs ... they look like duplicated. Is there by any chance this is done accidentally or they have a purpose?

One PATCHes the node (probably inputs and inputNodes) and the other one PATCHes the study (ui entry)

[pcrespov]

nice.
From the animationsI noticed that when you add a node, the PATCH request they seem to run in pairs ... they look like duplicated. Is there by any chance this is done accidentally or they have a purpose?

One PATCHes the node (probably inputs and inputNodes) and the other one PATCHes the study (ui entry)

But according to that it should have different path for the node and the study resp., right?

[sanderegg]

cool!

[GitHK]

Someone needs to monitor if this has any impact on the backend logic.

[odeimaiz]

nice.
From the animationsI noticed that when you add a node, the PATCH request they seem to run in pairs ... they look like duplicated. Is there by any chance this is done accidentally or they have a purpose?

One PATCHes the node (probably inputs and inputNodes) and the other one PATCHes the study (ui entry)

But according to that it should have different path for the node and the study resp., right?

@pcrespov

I better show you live

[matusdrobuliak66]

💯