JaeGeunBang opened a new pull request, #36094: URL: https://github.com/apache/superset/pull/36094
<!--- Please write the PR title following the conventions at https://www.conventionalcommits.org/en/v1.0.0/ Example: fix(dashboard): load charts correctly --> ### SUMMARY <!--- Describe the change below, including rationale and design decisions --> I add ALERT_REPORT_SLACK_V2: True in FEATURE_FLAGS. ``` FEATURE_FLAGS = { "ALERT_REPORT_SLACK_V2": True } ``` After switching to the Slack V2 API, I'm now sending .csv files via Superset Reports. The following issue has occurred. Slack should display the data as CSV, but it's being displayed as plain text. Note that this issue didn't occur in Slack V1. Please see the screenshot below. So, I discovered the issue in the Slack V2 code, fixed it, and confirmed that the CSV file is now displayed properly in Slack. ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF <!--- Skip this if not applicable --> Slack V1 <img width="695" height="680" alt="스크린샷 2025-11-13 오후 12 36 27" src="https://github.com/user-attachments/assets/7ad609ec-9772-4df2-a7c8-10aa37fd0f0d"; /> Slack V2 <img width="631" height="827" alt="스크린샷 2025-11-13 오후 12 36 34" src="https://github.com/user-attachments/assets/61266231-4744-4d80-adb7-7920172e2767"; /> ### TESTING INSTRUCTIONS <!--- Required! What steps can be taken to manually verify the changes? --> ### ADDITIONAL INFORMATION <!--- Check any relevant boxes with "x" --> <!--- HINT: Include "Fixes #nnn" if you are fixing an existing issue --> - [ ] Has associated issue: - [ ] Required feature flags: - [ ] Changes UI - [ ] Includes DB Migration (follow approval process in [SIP-59](https://github.com/apache/superset/issues/13351)) - [ ] Migration is atomic, supports rollback & is backwards-compatible - [ ] Confirm DB migration upgrade and downgrade tested - [ ] Runtime estimates and downtime expectations provided - [ ] Introduces new feature or API - [ ] Removes existing feature or API -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
