Solution Are; #1036

1. Modify the Data Size Limit
   Identify the part of the code where the 2MB limit is enforced.

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.

2. Add an Option to Disable Styling
   Locate the existing HTML rendering logic where styles are applied.

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.

3. Enable Custom Formatting
   Modify the ArrayFormatter or introduce a parameter (e.g., custom_formatter) that allows users to pass their own formatting function.

Ensure that the custom function is validated and safely applied without breaking existing functionality.

4. Refactor HTML Generation Code (Nice-to-have for maintainability)
   Break down the existing monolithic HTML rendering function into smaller, reusable helper functions.

Consider moving the HTML-related functions into a separate module/file if the changes become too extensive.

5. Testing & Documentation
   Write test cases to ensure the new functionalities work as expected.

Update the documentation with clear examples on how to:

Set a custom data size limit.

Disable styling.

Use a custom formatter.