-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Route parameters not used correctly? #2575
Comments
Is that ObjectId from MongoDb? I believe it has changed rather than swashbuckle? |
Please provide a minimal reproducible example as a GitHub repository that demonstrates the issue you're experiencing so we can look into this further. |
This issue is stale because it has been open for 60 days with no activity. It will be automatically closed in 14 days if no further updates are made. |
This issue is stale because it has been open for 60 days with no activity. It will be automatically closed in 14 days if no further updates are made. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
This works:
Request URL:
https://localhost:5001/api/v1/foo/907306994157748224
This doesn't:
Request URL:
https://localhost:5001/api/v1/foo/{id}?id=907306994157748224
Note the {id}?id=... in the above url.
The only difference is
long
vsObjectId
in the controller method. I am still git-bisecting and figuring out what changed; but this did work a year ago. TheObjectId
can be (implicitly) cast from/to a long.Oh, I also tried adding
[FromRoute]
to the argument to no avail.Has something changed?
The text was updated successfully, but these errors were encountered: