Jordan Kiesel

This ended up being resolved by #642, so this PR can be closed.

This appears to be an issue with the way Prettier itself loads plugins: prettier/prettier#15141 A workaround is to install the plugin in your home directory instead of globally. That seems...

@clementdessoude I'm curious what your thoughts are on the formatting decisions I made here. Could you take a look, whenever you have the time?

This appears to be identical to #630. See my response there for a temporary workaround.

Closing as duplicate of #630.

Prettier JavaScript keeps the comment in this position ([example](https://prettier.io/playground/#N4Igxg9gdgLgprEAuEBLAZgAgBQwE4CucAlJsADpTkwY75GkVSYusu3aVveuoDOAQQAmQgHIQhcTADJpXHt2yiA8gBEAogH0AwgIBKqgHRwAjgQCGAGz4BJAOZQIeONvN842R5IAy5gEZwlqQAPsHyCgoqGpoACup6AMrKosZmVrYOTi5uHl5wvgFBmKHhEdxRWgKqqnrqCQmpFtb2js6u7p4S+f6BIWHMZTwVsQASyeqN6S1Z7bldBb3F-YNDalpjAKoJ6mPeRqZNGa3ZHXkLQcSlbIxXrAC+mIHumBz84pIxeBAADtoAFuYoHYpLJMABCBL4VBAjY0ayGfjqAC23xgAE9sMCYJ8fnA8DQ4II+JC8NC7NhzAQhKgYMQ6WRbjxIFA+DBMN8vt8SWTMABeTBYnHfPEEoncoEUqk04gAbkZ3GZrMwAGs4GjRAQkQE8HyXplnBsCKghHxsBzUEjzHg0QBpNWy+VsZx8b7Qdziuy6j2GdBOS0wTggf6A4GYGAQTAxZQJGyqJCYACkfEwAFpE3xyCAADQqtUarV4nMcn4eh0DHh3eUAeirmAEMChfgI8GT2AA7n9UGA-pgrVJnJZzDQ3Zdy9wnlJXoIRHpAkPUNAZNIXoIG6Sm-AACpo4U3McRGuYTcADSPcBRg-g8YScBg3ggaKs6PrjebcE0AkdrEPN-PycsqCqmGnbJm2qCWJYvbWBGAJQEIlhSBsUBVuoUBfBBmDaAQrIQEieK9nBmCiPO0BWLObZWiaX4sIqbJDvgxF4bqWIvuub6MR4lLUrScr7gozquiycAel6UJAj6fpDoGrGoBuUhJr2IhwEImBgTAPYAG5WEQ6aZjm9F4BxRacgAatpJC8REDwTi8WDYPwwZAnAs6XguzCgvwMlyduu4MnxLCVmOgV3NmIA-MOLLIKAVpfG2MR9pFKBWBRaJ8KFfh4OYYCqjACTmHh3jQnAyDoOkcBZiAGVZTlCTfFlZLIPQ5UgO4SKoI1hDNXAAAewqknhsBWJueJQFaqCEiVZUVXwZIIQAigQEDwJN1jNQAVnw3UJLNcALUtxVIKVq0VWY+1CmlSV8CmUBwMpymhfg5jgWS2i4ZayAgFYlihTNQIIV5b4xHihU3St7gVX8MBIpYADqnYtnVYDCQgM00BpNJoh9YB8GlFUaUQNhwQguVgKSqICHBkJoghYPNcW7gw5l3wfRyhJ4hpxUVdC7j4p85h2O9h1TSAdV4DzH3osKfCk6gqKheasAw8a6nIAAHAADBVzhmKgzh8wL5i0xVMD+ErQgq0gAAsFXYXAm7+BdR3gyA54BEpQi+ECFjAgAYpJDYNUlzYQCAdx3EAA)), so I don't think we will change the formatting of this. We could potentially update the Checkstyle configuration that we provide.

I'm leaning towards simply removing the Checkstyle configuration that this repo provides. We haven't been maintaining it, and IMO there isn't really a good reason for Prettier Java to provide...

Sorry, I'm not sure how I messed up that user mention, I meant to direct that question to you. To clarify my question, I'm not asking why one would want...

A simple workaround is to provide a prefabricated value for BigInteger. For example: ```java package com.jparams.verifier.tostring; import org.junit.jupiter.api.RepeatedTest; import java.math.BigInteger; final class ToStringVerifier_BigIntegerTest { @RepeatedTest(15) void testBigInteger_toStringMethod() { ToStringVerifier.forClass(BigInteger.class).withPrefabValue(BigInteger.class, BigInteger.valueOf(1)).verify();...

As I understand it, this would require us to provide a CommonJS module in addition to our current ECMAScript Module. Normally, I think this would be as "simple" as transpiling...