Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Entities and documentation seem like a logical unit. Combining inheritable exposures with inheritable docs would be magical! I am currently forced to define a hash (object_fields) in a call to desc and maintain an entity and documentation separately.
My current work flow
Inevitably, our very immature API requires field fiddling and I have to revisit the entity. Suddenly I'm faced with the very frustrating prospect of changing the desc and the entity ... and I don't always remember. When I add something to the entity, I need to remember to add it to the object_fields hash as well.
If entities become aware of one more key, maybe called documentation, I could gain immediate visibility into which fields are and aren't documented... and I'd be happier.
Consequently, I'd now be able to easily include my documentation in my desc block