Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

Test summary

18159 • 0 • 214 • 7 • 4

Run details

View run in Cypress Dashboard ➡️

Flakiness

	cypress/integration/commands/net_stubbing_spec.ts		4
1	network stubbing > intercepting request > can intercept utf-8 request bodies without crashing
2	network stubbing > waiting and aliasing > can timeout waiting on a single request using "alias.request"
3	network stubbing > waiting and aliasing > can timeout waiting on a single request using "alias.request"
4	network stubbing > waiting and aliasing > can timeout waiting on a single request using "alias.request"

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

@tgriesser I will pick this up and get it green so we can merge it into unified-desktop-gui. Let me know if there was anything else you wanted to work on. I think this is in a good enough place to merge up (into the feature branch).

@lmiller1990 I had been starting to work on getting this so we can mount "fragments" for testing: 21206bd and adding SDL definition directives to Nexus so that we can specify what the "test values" should be in the server definition in a way that the frontend schema can consume.

Unfortunately the timing on this work hasn't mapped well to my PTO this week and last.

So feel free to pick it up from here for now - also was having trouble seeing how Vue validates props, either with the props definition or in the fragment use. Seemed it was very easy to use invalid values in the template without any sort of type or runtime errors/warning.

@tgriesser nice to see the test scaffolding. I'll get this back to ✅ , always good to keep things passing before it goes too out of sync.

As for Vue, I've found you can use PropType and a VS Code extension called Volar to get template validation in your IDE. I am sure there's some way to tweak tsconfig.json to error out when there are invalid types during the build step, too.

The prop validator key is most useful for when working with JS - similar to propTypes in React. I am not sure it will be too useful here, but it's possible to throw an error inside it if you want to be really defensive.