Add wait for API response before code sync

[tplevko]

Add wait for API response before the code-sync is performed to the e2e tests.

[codecov]

Codecov Report

Merging #1879 (1b602fd) into main (ac1a3c3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1879   +/-   ##
=======================================
  Coverage   57.93%   57.93%           
=======================================
  Files          70       70           
  Lines        2439     2439           
  Branches      566      566           
=======================================
  Hits         1413     1413           
  Misses        976      976           
  Partials       50       50           

[lordrip]

@tplevko, do you think that it might be a good idea to introduce the "busy" concept as a matter to signal that the UI is doing something?

It might not be available for all circumstances and also we would need to check if impacts negatively the UI, but apart from that, I'm wondering if that would be helpful for the e2e.

The way that I imagine it, is that whenever you hit the sync button, there's an attribute set as "busy" and whenever the response is back, we switch it to "ready" or something like that. Maybe we could do something like that for the canvas as well.

[tplevko]

In case it wouldn't negatively impact the UX, the "busy" concept could be a way to go. However for now I'd maybe leave as it is - the issues are only related to e2e tests, which are interacting with the UI "too quickly", causing the syncing issues with the backend, so I hope this could be solved with the waits for API responses.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[lordrip]

Sorry @tplevko, I didn't meant for you to do it 😄 , I meant if it could be helpful for the e2e in the future, so I could start thinking on that and makes our lives easier and tested