[Feature] Use ancestor/descendant terminology in YAML selectors instead of parent/child

[dbeatty10]

Is this your first time submitting a feature request?

• I have read the expectations for open source contributors
• I have searched the existing issues, and I could not find an existing issue for this feature
• I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature

Here's essentially what our docs currently say for YAML selectors:

definition:
  method: tag
  value: nightly

  # The following optional keywords map to the `+` and `@` graph operators:
  parents: true | false
  children: true | false
  parents_depth: 1                    # + operator (left-hand side) -- degrees to include IFF parents: true
  children_depth: 1                   # + operator (right-hand side)-- degrees to include IFF children: true
  childrens_parents: true | false     # @ operator -- includes all ancestors of all descendants IFF true

This feature request is to replace:

• parents with ancestors
• children with descendants
• parents_depth with ancestors_depth
• children_depth with descendants_depth
• childrens_parents with descendants_ancestors

Describe alternatives you've considered

Let sleeping dogs lie.

That's probably what we will do here! 🐶

Who will this benefit?

Anyone confused by what "parents" or "children" actually includes (since it has a different meaning than the standard human parent/child relationship).

For example: #7703 (comment)

We already updated some of the docs in dbt-labs/docs.getdbt.com#3755 / dbt-labs/docs.getdbt.com#5313

Are you interested in contributing this feature?

No response

Anything else?

No response

[dbeatty10]

Here's where to find the relevant code:

• https://github.com/search?q=repo%3Adbt-labs%2Fdbt-core+parents_depth&type=code
• https://github.com/search?q=repo%3Adbt-labs%2Fdbt-core%20children_depth&type=code

Although it doesn't look like it involves a ton of code, the juice doesn't seem worth the squeeze, so I'm going to close this as "not planned".

Rather, we can address with clarifying language within the docs for YAML selectors as-needed.

If anyone disagrees, please reach out 😃

[dbeatty10]

Made an update to the product documentation via dbt-labs/docs.getdbt.com#3755 and dbt-labs/docs.getdbt.com#5313