Feature.proto should have a description field #3277
Description
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I would like to attach a human-readable description to each field in a feature view. Since data scientists shop for individual features and not feature-views, it's useful to have documentation associated with each feature individually (rather than for the entire feature view). Persisting it here will allow us to surface them in various UIs.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Similar to Entity.proto, we should add a description field to features and store them in the registry.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
For now, we're just using a description tag on each feature. This works, but it's clunky. It also means that in our UI, we have to remove certain tags before showing the raw tags to the users.
Additional context
Add any other context or screenshots about the feature request here.