Alec Wilson

I can replicate this on release 1.7.1 and directly on master - but not on the demo site http://parsedown.org/demo. There it has the same behaviour as Markdown PHP 1.3 and...

Looks like this can be fixed by amending the `$EmRegex` to exclude matches that start/end with whitespace. The current regex is ``` protected $EmRegex = array( '*' => '/^[*]((?:\\\\\*|[^*]|[*][*][^*]+?[*][*])+?)[*](?![*])/s', '_'...

I'd also find this feature useful. Taking a look at the code it looks like the behaviour change would be within https://github.com/vektra/mockery/blob/8174e46cfded8b352b05339478e6263e30cbecc8/pkg/walker.go#L65 I'd have a stab at a PR on...

I'd vote for option 2, I hadn't even thought of that alternative! Imagining code to support this would be simpler which is a big plus. Although config might be more...

PR opened for implementing `.mockery_skip`. First time contributing something more than a trivial doc change to OS so any guidance on improving the PR description / approach very welcome 🙂

> @alec-w checking back up on this PR, I think this is a great feature and was wondering if you'd have time to take a look at the comments I...

I'm still getting to grips with the generator code. This feels a bit of a hack (we strip the slice markers and replace them with ellipses if we have figured...

Believe the linked PR may be a way to resolve this - but could do with some thoughts on whether this is the best way to resolve this, feels like...

The PR I've just opened resolved the issue around the given_name and family_name for us (and it could be updated to add the preferred_username as well). Could do with some...

> Maybe there is a better way I agree, that was more a hack that worked enough for me to continue with some local testing > In cognito it might...