-
Notifications
You must be signed in to change notification settings - Fork 37
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
Path strings should be quoted or have whitespace escaped #254
Comments
I think you need to follow this https://github.com/Azure/openapi-diff#how-to-install to install the latest version tool |
Thanks. So I shouldn't expect the version that's currently in the npm repository to work? The docs I'm following suggest to install this tool via npm rather than installing manually via the repository. I could request these docs be updated, but on further inspection, the version on npm is quite old. Would it be possible to make a new npm release? I'm fine to try manual installation, but installing via npm seems better for future users. |
I think the doc has been updated for long time, currently we push the tool to '@azure/oad', not 'oad'. You can still retrieve the latest version from npm |
Thanks, that helps. I've just uninstalled the old version and installed the correct latest from
|
Thanks, it's a bug, we should escape the space in the return of this function
|
Actually, a better change as opposed to quoting or escaping whitespace would be to use less a less fallible API like execFileSync instead of execSync (or async variants) |
Environment:
oad
fromnpm install -g oav
. I've never used it before. Version installed was0.1.9
.When I run
oad compare my-old-spec.json my-new-spec.json
as per the instructions, I get the file not found errors. If I manually create these files out of curiosity, I still get an error.The text was updated successfully, but these errors were encountered: