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

When using -d to pass in the config #297

Closed
SteveL-MSFT opened this issue Jan 19, 2024 · 1 comment · Fixed by #380
Closed

When using -d to pass in the config #297

SteveL-MSFT opened this issue Jan 19, 2024 · 1 comment · Fixed by #380
Assignees
Labels
Issue-Enhancement The issue is a feature or idea

Comments

@SteveL-MSFT
Copy link
Member

Summary of the new feature / enhancement

-i is intended for JSON content while -p is the path to a JSON file. Users may mix this up, so when using -i, if it's not valid JSON, we should check if it's a valid filepath and if so, inform in the error message it looks like a filepath and they should use -p instead. Similarly, if -p doesn't find the file, see if the input is JSON and give better error message.

Proposed technical implementation details (optional)

No response

@SteveL-MSFT SteveL-MSFT added the Issue-Enhancement The issue is a feature or idea label Jan 19, 2024
@SteveL-MSFT SteveL-MSFT changed the title When using -i to pass in the config When using -d to pass in the config Apr 3, 2024
@SteveL-MSFT
Copy link
Member Author

Parameter was changed to -d but the scenario still exists

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Enhancement The issue is a feature or idea
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant