-
Notifications
You must be signed in to change notification settings - Fork 110
Improve html table rendering formatting #1078
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Solution Are; #1036
Introduce a user-configurable parameter (e.g., max_data_size), allowing users to set their preferred limit. Ensure that the size approximation logic remains efficient and does not slow down performance.
Introduce a flag (e.g., disable_styling) that allows users to enable or disable CSS styling in the output. Implement a conditional check to apply styling only if the flag is not set.
Ensure that the custom function is validated and safely applied without breaking existing functionality.
Consider moving the HTML-related functions into a separate module/file if the changes become too extensive.
Update the documentation with clear examples on how to: Set a custom data size limit. Disable styling. Use a custom formatter. |
Closed due to the excellent work by @kosiew |
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
This is a follow on to #1036
There is a suggestion that we should enable a feature to customize the html table rendering.
Describe the solution you'd like
Allow the user to set the amount of data returned. Right now it's hard coded to 2 MB. The actual data size is approximated. We would like this to be customizable.
Allow the user to disable the styling that is applied to the html output.
Optional: Add a way for a user to specify a formatting function to replace the default
ArrayFormatter
. This would enable users to change the data view when they have custom metadataNice to have: Split up some of the html generation into a set of helper functions.
Describe alternatives you've considered
None
Additional context
If this code is getting too large, it may make sense to split it off into a separate file.
The text was updated successfully, but these errors were encountered: