# \[FEATURE\]Custom Props/Parameters Property Editor Tooltip

**URL:** <https://forum.inductiveautomation.com/t/feature-custom-props-parameters-property-editor-tooltip/71522>\
**Category:** Ignition\
**Tags:** perspective, ignition81\
**Created:** [March 23, 2023, 7:25pm UTC](https://forum.inductiveautomation.com/t/feature-custom-props-parameters-property-editor-tooltip/71522 "2023-03-23T19:25:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\
**Post date:** [March 23, 2023, 7:25pm UTC](https://forum.inductiveautomation.com/t/feature-custom-props-parameters-property-editor-tooltip/71522/1 "2023-03-23T19:25:11Z")

</div>

I remember seeing a post about parameter types where the user had a string that was actually a number, but could not explicitly call out the parameter as an int and something for this was in the works.

I would also like to propose that a "description" field be available for each custom parameter/property that shows as a popup when hovering over it in the property editor, similar to the way it does for default props.

This would be super convenient to document the purpose of each of the parameters/custom props for later (when I inevitably come back in 8 months and have to remember how everything is put together).

[FEATURE](https://ideas.inductiveautomation.com/ignition-features-and-ideas/p/custom-props-properties)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 23, 2023, 9:25pm UTC](https://forum.inductiveautomation.com/t/feature-custom-props-parameters-property-editor-tooltip/71522/2 "2023-03-23T21:25:34Z")

</div>

This would come "for free" with the planned enhancement; all of the JSON editing niceties you get with Perspective components are available because each component provides a JSON schema, which outlines expected types, possible values for pseudo enums, etc. Once that's available to you, adding descriptions (which we'll present as tooltips) is easy.