Trevor Radcliffe

I have one rule for markdownlint I'd like for engineers to be aware of, but I don't want our pre-merge lint checks to fail and prevent submission...Specifically the inline html...

That works. It seems kind of like a hack, but I'm sure you have a lot going on and need to prioritize. I get that some less important requests, more...

Some responses to that comment: > I am fine with adding a new column for "bazel", or a new column for "CLI", but it's even better if "bazel" piggybacks on...

Relevant discussion in https://github.com/diffplug/spotless/issues/529#issuecomment-589685889 Hmmm...I see your point. I will definitely take these things into consideration. I feel really weird using a Gradle build script as a configuration for another...

Wait, does the ruby version even allow the inline disabling of rules like the Node project does?

Ok. Because of its nature as a more prose-oriented language, I could see this being the case, but how specifically do you see markdown as different from other languages in...

I'm still a little skeptical of differentiating these kinds of test as "analysis test" vs "unit test". I see the analysis tests as being unit tests for rules, whereas "unit...

Any update on this? This would be a very nice feature and it looks like it's complete. Is there a reason it hasn't been merged yet?

Hey y'all, I think I'm fairly close to a solution proposal for this, but I wanted to make sure that what I have in mind actually meets the needs of...

@tpudlik Can you give me more detail about your last comment? I took a look at the issue you linked, and I'm not sure how the functionality described there doesn't...