The codebase carries several deprecated aliases that emit DeprecationWarning — Field (fairgraph/fields.py), the fields/field_names/required_field_names/existence_query_fields classmethods and Node (registry.py), RepresentsSingleObject (base.py), EmbeddedMetadata (embedded.py), and the scope keyword (utility.py).
What is missing is the policy: which names are deprecated, when each was deprecated, and in which release it will be removed. The scope keyword's warning already promises removal "in version 1.0", so the intent exists but is scattered across warning strings.
A table in the documentation would make the contract legible, and gives users something to plan against.
The codebase carries several deprecated aliases that emit
DeprecationWarning—Field(fairgraph/fields.py), thefields/field_names/required_field_names/existence_query_fieldsclassmethods andNode(registry.py),RepresentsSingleObject(base.py),EmbeddedMetadata(embedded.py), and thescopekeyword (utility.py).What is missing is the policy: which names are deprecated, when each was deprecated, and in which release it will be removed. The
scopekeyword's warning already promises removal "in version 1.0", so the intent exists but is scattered across warning strings.A table in the documentation would make the contract legible, and gives users something to plan against.