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.

Sign up for GitHub

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

Jump to bottom

Versions above >0.1.9 cannot start scenarios if spec file name contains spaces. #1056

Open
jensakejohansson opened this issue Mar 5, 2025 · 0 comments
Open

Versions above >0.1.9 cannot start scenarios if spec file name contains spaces. #1056

jensakejohansson opened this issue Mar 5, 2025 · 0 comments

Comments

@jensakejohansson
Copy link
Contributor

Breaking change / bug introduced in v. 0.2.0 and above resulting in that spec-files fail to launch in vscode if the spec-file name contains spaces.

Tested on Windows. To recreate:

  1. gauge init dotnet
  2. Rename file "example.spec" to "example 1.spec".
  3. Try to launch a scenario in vscode.
  4. Fails, seems to build build path incorrectly:

Image

When looking closer, there seems to be problems in older versions too if directory names contained spaces, but to not allow spaces in spec-file-name is a new bug.
@jensakejohansson jensakejohansson changed the title Versions above >0.1.9 cannot start scenarios if spec file contains a spaces. Versions above >0.1.9 cannot start scenarios if spec file name contains spaces. Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jensakejohansson