Skip to content

Deprecating a field in a paged result set should deprecate corresponding filter inputs. #8527

@bbarry

Description

@bbarry

Product

Hot Chocolate

Is your feature request related to a problem?

It would be nice if when we use [UseFiltering] that any fields that are marked deprecated in the record should be deprecated in the generated filter input type.

The solution you'd like

For example if I had:

[UseFiltering]
public async Task<Connection<Book>?> GetBooks( ... ) { ... }

public record Book(int Id, string? Name, [property: Obsolete("don't use this")] string? Foo);

then the schema should have:

input BookFilterInput {
  # ...
  Foo: StringOperationFilterInput @deprecated("don't use this");
}

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions