# Apex chart in Perspective component **URL:** \ **Category:** Module Development\ **Tags:** ignition81, perspective\ **Created:** [December 20, 2024, 5:03am UTC](https://forum.inductiveautomation.com/t/apex-chart-in-perspective-component/100081 "2024-12-20T05:03:15Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [January 5, 2025, 8:13pm UTC](https://forum.inductiveautomation.com/t/apex-chart-in-perspective-component/100081/4 "2025-01-05T20:13:50Z")
> [@Grace\_Gan](#): > > as it handles data querying within the component Ewww! Sounds like the same foolishness you've been advised against before (different components?): > [@Perspective component get dropdown props from gateway](https://forum.inductiveautomation.com/t/perspective-component-get-dropdown-props-from-gateway/99606/4): > > Seems like an anti-pattern. Components are best when they’re flexible, and making a component do its own queries is at odds with the goals of Ignition. Is there a reason you don’t want to provide your options through a binding? > [@Perspective Component](https://forum.inductiveautomation.com/t/perspective-component/98768/6): > > Ignition's query bindings are extraordinarily flexible. If you really want users to not worry about the behavior of the query inside your component, do not put the query inside your component. You are re-inventing the wheel. You are unlikely to do this as well as IA already did, with query bindings. Really. Don't have your component run its own queries. IA has some components that run their own queries. They are frustrating to use and utterly inflexible. Don't follow that example. You **really** shouldn't be doing this. --- _[View the full topic](https://forum.inductiveautomation.com/t/apex-chart-in-perspective-component/100081)._