Hey, . Thank you for suggesting this. I think path parameters matching in this way would be much more versatile and seamless for the developer. I wonder how TS works when that path string is dynamically constructed?
It looks like bumping to
typescript: 4.1.x wouldn't even be a breaking change, as we rely on
4.0.x at the moment. That being said, how should we handle such TypeScript updates for the consumers of the library? Should we specify a TypeScript version in the