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

--output-dir not working in v0.5.0 #243

Closed
3 tasks done
kmalaver opened this issue Nov 15, 2024 · 2 comments
Closed
3 tasks done

--output-dir not working in v0.5.0 #243

kmalaver opened this issue Nov 15, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@kmalaver
Copy link

First Check

  • This is not a feature request.
  • I added a very descriptive title to this issue (title field is above this).
  • I used the GitHub search to find a similar issue and didn't find it.

What is the issue you are experiencing?

In the last version the flag --output-dir is not working, the project is generated in the local path

Steps to Reproduce (or failing test case)

run scaffold new example --output-dir='"./my/custom/path"

Scaffold Version (scaffold --version)

v0.5.0

@kmalaver kmalaver added the bug Something isn't working label Nov 15, 2024
@hay-kot
Copy link
Owner

hay-kot commented Nov 18, 2024

This still works for me, the issue is with your command order I believe. It should be

run scaffold new --output-dir='"./my/custom/path" example 

Which is dumb, but it's a limitation of the CLI library I'm using. They've fixed this in v3 which is in pre-release right now.

I'm going to look into migrating to v3 over Christmas when I have some time off and have time for a nice refactor 😄

@kmalaver
Copy link
Author

it was indeed the order, thank you 🙌

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

No branches or pull requests

2 participants