Skip to content

Conversation

@radekdoulik
Copy link
Member

The new option allows to specify which types are processed by a
profile with the list of types (regex patterns) to process.

It is similar to specify multiple -t options.

The new option allows to specify which types are processed by a
*profile* with the list of types (regex patterns) to process.

It is similar to specify multiple `-t` options.
@radekdoulik radekdoulik requested a review from jonpryor August 7, 2018 21:02
typeNameRegexes.Add (new Regex (line));
}
} catch (Exception e) {
Error ($"Unable to read profile '{profilePath}'.\n{e}");
Copy link
Contributor

Choose a reason for hiding this comment

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

This is kinda crazy, but I have no idea what a \n is going to do on Windows, especially with our color-altering Error() method. Should this instead use {Environment.NewLine}?

Copy link
Member Author

Choose a reason for hiding this comment

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

{Environment.NewLine} makes sense. I will update it (and replace \n in other places too)

@jonpryor
Copy link
Contributor

jonpryor commented Aug 9, 2018

Why does this now have a Cecil bump?

@radekdoulik radekdoulik force-pushed the pr-add-profile-option branch from f87e02a to 7f8d655 Compare August 9, 2018 20:46
@radekdoulik
Copy link
Member Author

Ops, updated.

@jonpryor jonpryor merged commit d174fa6 into dotnet:master Aug 13, 2018
@github-actions github-actions bot locked and limited conversation to collaborators Apr 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants