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

VSCode extension fails to run FTL in ftl-examples repo #1621

Closed
alecthomas opened this issue Jun 2, 2024 · 1 comment · Fixed by #1651
Closed

VSCode extension fails to run FTL in ftl-examples repo #1621

alecthomas opened this issue Jun 2, 2024 · 1 comment · Fixed by #1651
Assignees
Labels
bug Something isn't working

Comments

@alecthomas
Copy link
Collaborator

image
@alecthomas alecthomas added the bug Something isn't working label Jun 2, 2024
@github-actions github-actions bot added the triage Issue needs triaging label Jun 2, 2024
@ftl-robot ftl-robot mentioned this issue Jun 2, 2024
@alecthomas
Copy link
Collaborator Author

I can only make this work by updating the extension setting for the ftl binary path to bin/ftl, even though ftl is in the active $PATH

@alecthomas alecthomas removed the triage Issue needs triaging label Jun 4, 2024
wesbillman added a commit that referenced this issue Jun 4, 2024
Fixes #1621

This seems to better identify which ftl to use based on what `which ftl`
returns for a given workspace.

> [!NOTE]  
> The path will not be detected correctly if a workspace is changed via
File->Open...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants