You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been considering how we can help users integrate their custom functions into Great Tables more seamlessly. One possible approach is to introduce register() and unregister() methods (just a rough concept for now), like:
For users who heavily rely on custom functions—or for third-party package maintainers working with Great Tables—having register() and unregister() methods could offer greater flexibility and convenience.
Hello team:
I've been considering how we can help users integrate their custom functions into Great Tables more seamlessly. One possible approach is to introduce
register()
andunregister()
methods (just a rough concept for now), like:Here’s a simple example:
Currently, users can apply custom functions using
GT.pipe()
, like:However, this feels more like a one-off approach.
For users who heavily rely on custom functions—or for third-party package maintainers working with Great Tables—having
register()
andunregister()
methods could offer greater flexibility and convenience.One thing to note is that we may need to consider how to improve modern IDE support to enhance autocomplete functionality in this context.
The text was updated successfully, but these errors were encountered: