Is your feature request related to a problem? Please describe.
The improvement in #391 made it much easier to understand metadata, but I noticed that the improved behavior didn't land for editing data files from the dashboard or inserting snippets. In both cases, the description key appears unused, neither appearing in the view nor when hovering over the inputs or their labels.
Describe the solution you'd like
I would like for the description key, when defined for input fields, to display in the same context similarly to how it does for content metadata fields. This would make it easier to understand what the inputs are for without having to refer to documentation.
Describe alternatives you've considered
Alternative to always displaying the description text, displaying that text when the user hovers on the label for that input would also be useful and possibly less disruptive to the UX, though also less discoverable I think.
Additional context
**Is your feature request related to a problem? Please describe.**
The improvement in #391 made it much easier to understand metadata, but I noticed that the improved behavior didn't land for editing data files from the dashboard or inserting snippets. In both cases, the **description** key appears unused, neither appearing in the view nor when hovering over the inputs or their labels.
**Describe the solution you'd like**
I would like for the **description** key, when defined for input fields, to display in the same context similarly to how it does for content metadata fields. This would make it easier to understand what the inputs are for without having to refer to documentation.
**Describe alternatives you've considered**
Alternative to always displaying the description text, displaying that text when the user hovers on the label for that input would also be useful and possibly less disruptive to the UX, though also less discoverable I think.
**Additional context**


<!-- github-sync-id:1401812033 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Is your feature request related to a problem? Please describe.
The improvement in #391 made it much easier to understand metadata, but I noticed that the improved behavior didn't land for editing data files from the dashboard or inserting snippets. In both cases, the description key appears unused, neither appearing in the view nor when hovering over the inputs or their labels.
Describe the solution you'd like
I would like for the description key, when defined for input fields, to display in the same context similarly to how it does for content metadata fields. This would make it easier to understand what the inputs are for without having to refer to documentation.
Describe alternatives you've considered
Alternative to always displaying the description text, displaying that text when the user hovers on the label for that input would also be useful and possibly less disruptive to the UX, though also less discoverable I think.
Additional context
Input descriptions should now appear on snippet forms and data forms in the latest beta version.