Problem using CSV containing BOM

[ganesh-bruno]

I have checked the following:

• I have searched existing issues and found nothing related to my issue.

This bug is:

• making Bruno unusable for me
• slowing me down but I'm able to continue working
• annoying

Bruno version

2.0.1

Operating System

Mac

Describe the bug

When using a CSV file exported from Excel that contains a Byte Order Mark (BOM), the file is not properly parsed in the first column. The BOM can cause issues with how the data is processed, making the first column unusable.

Steps to Reproduce:

1. Create a request and add the variable id in the JSON body.

2. Run the collection.

3. Use the provided sample.csv file.

4. Observe that the id is not interpolated correctly.

Expected Behaviour:
The CSV should be properly parsed, and the data from all columns, including the first column, should be usable without issues.

Actual Behaviour:
The first column is either unusable or contains unwanted characters due to the BOM being present in the file.

.bru file to reproduce the bug

Screenshots/Live demo link

CSV file:

sample.csv

[sreelakshmi-bruno]

Hi, this issue has been fixed in v2.2.0. Closing the issue as it's been resolved. Thanks!