Why is this feature valuable to you? Does it solve a problem you're having?
The generated test code currently checks all structs, but doesn't really do anything with routes. We use the generated tests to verify semver compatibility, but a change to a route's argument types would be semver-incompatible but not caught by the tests.
Describe the solution you'd like
A simple compile-only "test" that calls the route with a no-op client and ignores the result would be sufficient to validate that the types are correct.
Describe alternatives you've considered
n/a
Additional context
Recent spec update changed the args to files::upload (semver incompatible) and we only caught it because one of the hand-written integration tests calls that function.
Why is this feature valuable to you? Does it solve a problem you're having? The generated test code currently checks all structs, but doesn't really do anything with routes. We use the generated tests to verify semver compatibility, but a change to a route's argument types would be semver-incompatible but not caught by the tests.
Describe the solution you'd like A simple compile-only "test" that calls the route with a no-op client and ignores the result would be sufficient to validate that the types are correct.
Describe alternatives you've considered n/a
Additional context Recent spec update changed the args to
files::upload(semver incompatible) and we only caught it because one of the hand-written integration tests calls that function.