graphql-python / graphql-python/graphene
Can I use deprecation_reason in InputObjectType?
Open
Nobody has claimed this yet.
🐛 bug
- Dominant language
- Python
- Stars
- 8.2k
- Forks
- 818
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I want to mark some fields as "deprecation_reason" in my filter fields.
example:
TestQuery{
filter:TestFilter
}
TestFilter{
id: IntFilter,
name: StringFilter
}
StringFilter = type("String", graphene.InputobjectType, {key:value})
How can I mark "name" is "deprecation_reason"?
thanks
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the InputObjectType and deprecation_reason entry points in Graphene. Determine whether fields in the example TestFilter can receive a deprecation reason, and document the supported usage or clarify that it is not available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, python
- Domain
- api
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100