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

Parse html errors #360

Merged
merged 2 commits into from
Jan 4, 2019
Merged

Parse html errors #360

merged 2 commits into from
Jan 4, 2019

Conversation

ejizba
Copy link
Contributor

@ejizba ejizba commented Jan 2, 2019

See test cases for example errors and what they look like now.

Fixes microsoft/vscode-azurefunctions#841
Related microsoft/vscode-azurefunctions#878

@ejizba ejizba requested a review from a team as a code owner January 2, 2019 22:45
@@ -34,6 +34,7 @@
"azure-arm-resource": "^3.0.0-preview",
"azure-arm-storage": "^3.1.0",
"fs-extra": "^4.0.3",
"html-to-text": "^4.0.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel this should be locked down, without the ^. There's quite some test code that essentially tests this package's functionality (rather than how we use it). A package update making our code fail (if the parseIfHtml behavior changes subtly) is more overhead, especially for this upstream repo which can break the downstream extensions.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's what the package-lock.json is for

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants