Skip to content
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

[BUG] Error when naming Request starting with "/" #1336

Open
jahirvidrio opened this issue Jan 5, 2024 · 1 comment
Open

[BUG] Error when naming Request starting with "/" #1336

jahirvidrio opened this issue Jan 5, 2024 · 1 comment
Labels
bug Something isn't working module-file-naming

Comments

@jahirvidrio
Copy link

Description

I am currently using version 1.6.1 on MacOS. I have encountered a bug where attempting to name a REQUEST with any name starting with "/" results in the following error:

Error invoking remote method 'renderer:new-request': Error: ENOENT: no such file or directory, open '/Users/**/Desktop/collections/My Collection/My Folder//auth/sign-in/lookup.bru'

I've identified that the method used to create the file path is concatenating the literal name I provided with the relative project path. It seems that there is an issue with the concatenation process, leading to the creation of an incorrect file path.

Steps to Reproduce

  1. Attempt to create "New Request" or "Rename" existing request
  2. Enter a name for the request that starts with "/" (e.g., "/example").

Expected Behavior

Creating a request with a name starting with "/" should not result in a file path error.

@Its-treason
Copy link
Member

Bruno currently has some issues on escaping filenames (like removing other invalid characters from the filename on Windows). There is already a PR open to fix this issue: #349, but this may need some time to be merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working module-file-naming
Projects
None yet
Development

No branches or pull requests

4 participants