`@Deprecated()` decorator not working with `@FormField()`
See original GitHub issueSorting
-
I’m submitting a …
- bug report
- feature request (? I let you decide)
- support request
-
I confirm that I
- used the search to make sure that a similar issue hasn’t already been submit
Expected Behavior
Usage of @Deprecated()
on @FormField()
should set deprecated: true
correctly, like in the doc here.
Example:
@Get("v2")
public async findV2(
@FormField() text: string,
@Deprecated() @FormField() dontUse?: string
): Promise<any> {
}
Current Behavior
No deprecation is generated in openapi.json
.
Context (Environment)
Version of the library: 4.1.3 Version of NodeJS: v16.17.1
- Confirm you were using yarn not npm: [ ]
Issue Analytics
- State:
- Created 10 months ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
SubfieldBase has been deprecated - Stack Overflow
The problem is in this line: class GeopositionField(with_metaclass(models.SubfieldBase, models.Field)):. Change it to:
Read more >Deprecated decorator's message does not appear · Issue #1411
Expected behavior When we run a method or class has deprecated decorator of optuna, we expect a warning message is shown.
Read more >TextFormField class - material library - Flutter - Dart API docs
This is a convenience widget that wraps a TextField widget in a FormField. A Form ancestor is not required. The Form simply makes...
Read more >Deprecated List (Magnolia UI (parent) 6.2.21 API)
Since 8.1, will be replaced by FileDropTargetExtension and FileDropEvent, https://github.com/vaadin/framework/issues/8891.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Would you like to submit this as a PR?
I’ll check but it should work just fine. If you check the CI we are running the tests in node 16.