Closed Giuliopime closed 12 months ago
Can we ignore those failed checks? First two are just in an example server, the others "conflicting declarations" aren't actually conflicting 'cause one requires a typed parameter
Can this be part of the next release with the previous pr too? Did you have any specific plans for the release?
I usually dont have any specific plans and create new versions as soon and often as possible - i.e. as soon as anything changed or was added. I'll create a new release for this pr (probably) tomorrow. All other changes should already have been released and included in the latest version.
It seems like it's not behaving correctly, if I add a queryParameter to a resource route, it will add both the queryParameter (correctly) and an identical path parameter that shouldn't be there
There seem to be an automatic resources class conversion which shouldn't be there
Temporary fix for #56