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

aiken blueprint apply works with the 1st parameter only #927

Open
1 of 4 tasks
Fell-x27 opened this issue May 8, 2024 · 5 comments
Open
1 of 4 tasks

aiken blueprint apply works with the 1st parameter only #927

Fell-x27 opened this issue May 8, 2024 · 5 comments
Labels
tooling Tooling and developer experience improvements

Comments

@Fell-x27
Copy link

Fell-x27 commented May 8, 2024

What Git revision are you using?

aiken v1.0.26-alpha+075668b

What operating system are you using, and which version?

  • Linux / Ubuntu
  • Linux / Other
  • macOS
  • Windows

Describe what the problem is?

The aiken blueprint apply asks only for the first parameter and ignores others.

What should be the expected behavior?

The command should parse more than one parameter.

@KtorZ
Copy link
Member

KtorZ commented May 8, 2024

That is the expected behavior. Parameters are applied one-by-one, and the command must be called multiple times. One for each parameter.

This isn't set in stone, but I'd like to understand what problems does this cause?

@KtorZ KtorZ added the waiting on response Waiting on author to respond to comments label May 8, 2024
@Fell-x27
Copy link
Author

Fell-x27 commented May 8, 2024

but I'd like to understand what problems does this cause

  1. It doesn't update the blueprint by itself, so if I call it twice, the second attempt will be the same as the first one.
  2. Yes, it shows the updated blueprint in CLI, so I can write it to the file manually, but if I call it like

aiken blueprint apply -v oneshot.gift_card > plutus.json

I get:

    Analyzing blueprint
    Summary 1 error, 0 warnings

in the output and...

 × EOF while parsing a value at line 1 column 0
help: EOF while parsing a value at line 1 column 0

in the file, so the blueprint has been destroyed.

Looks like there is some kind of a bug anyway.
Yes, I can rewrite the blueprint by many other ways, even with copy-paste, but it's a UX problem anyway I think. Writing with ">" shouldn't act like this...

@Fell-x27
Copy link
Author

Fell-x27 commented May 8, 2024

Oh, I see, there is the -o flag for this. But it's still a UX issue. It would be much better if it allowed setting all parameters within the same call step by step, and then asked for the filename to save, using the old one by default. This would provide a smoother and more user-friendly experience.

@rvcas
Copy link
Member

rvcas commented May 9, 2024

@Fell-x27 thanks for the comments, we'll give this some thoughts and see what we can cook up using your advice

@rvcas rvcas added tooling Tooling and developer experience improvements and removed waiting on response Waiting on author to respond to comments labels May 9, 2024
@Fell-x27
Copy link
Author

@Fell-x27 thanks for the comments, we'll give this some thoughts and see what we can cook up using your advice

Thanks. Just want to say - I'm totally in love with Aiken, guys! You did an amazing work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tooling Tooling and developer experience improvements
Projects
Status: 🔨 Todo
Development

No branches or pull requests

3 participants