[Feature Request] Clarify inheritance rules/reasons for workflow attributes
cretz opened this issue · comments
Describe the solution you'd like
It's not as clear as it could be in README that 1) we intentionally do not inherit an parent's [Workflow] attribute or [WorkflowRun] method, 2) why we don't, 3) that we do allow inheriting workflow signals/queries from base classes, but if overridden must have attributes, and 4) why for that too (i.e. their value for shared code reasons).
Maybe a "Workflow Inheritance" section in README is warranted.