When opening a large Excel file, we can use chunk processing to break the response into smaller chunks and send them in parallel to the client. Our current chunk processing handles large datasets by processing each chunk independently, sending a single request to initiate processing for each chunk sequentially. In this current process, the beforeOpen event will be triggered only once at the start of the chunk processing. In this scenario, the user can only add the header once for the whole chunk processing.
To enhance flexibility, we need to implement an enhancement where the beforeOpen event will be triggered each time for every chunk so that the user can add headers for each chunk request.
Additionally, we need to consider scenarios where a threshold limit is set using maximumDataLimit or maximumFileSize. In such cases, a confirmation dialog is shown to the user before continuing with the import process. We propose that the beforeOpen event should also be triggered after the user confirms and proceeds with the file processing, ensuring consistent behavior and allowing users to reapply headers or logic as needed.
