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

fix: output with warnings and env vars #148

Merged
merged 1 commit into from
Apr 5, 2023

Conversation

gitphill
Copy link
Contributor

@gitphill gitphill commented Apr 5, 2023

Fixing bug when mvn output contains unresolved properties, i.e.
'${my.prop}'.

@gitphill gitphill force-pushed the fix/parse-warnings-and-env-var branch from 9df21f9 to c352378 Compare April 5, 2023 14:37
@gitphill gitphill marked this pull request as ready for review April 5, 2023 14:37
@gitphill gitphill requested a review from a team as a code owner April 5, 2023 14:37
@gitphill gitphill force-pushed the fix/parse-warnings-and-env-var branch from c352378 to cdf5983 Compare April 5, 2023 15:03
Fixing bug when mvn output contains unresolved properties, i.e.
'${my.prop}'.
@gitphill gitphill force-pushed the fix/parse-warnings-and-env-var branch from cdf5983 to ad05525 Compare April 5, 2023 15:15
@@ -0,0 +1,6 @@
const regex = /digraph([\s\S]*?)\}[\s]*?$/gm;
Copy link
Contributor

Choose a reason for hiding this comment

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

Nitpick: could it be cleaner to parse based on "? Something like "[^"]*" ?

@gitphill gitphill merged commit 309b64b into master Apr 5, 2023
@gitphill gitphill deleted the fix/parse-warnings-and-env-var branch April 5, 2023 15:25
@snyksec
Copy link

snyksec commented Apr 5, 2023

🎉 This PR is included in version 2.32.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

4 participants