Uh oh!
There was an error while loading. Please reload this page.
[Java][Spring][#2901] remove unused import from spring template - #3843
[Java][Spring][#2901] remove unused import from spring template#3843bilak wants to merge 1 commit into
Conversation
9b4c3ee to
ce3b7c5Comparebilak
commented
Sep 6, 2019
@wing328 is it possible to add this pr to upcoming release? |
bilak
commented
Sep 10, 2019
cc @bbdouglas (2017/07) @sreeshas (2017/08) @jfiala (2017/08) @lukoyanov (2017/09) @cbornet (2017/09) @jeff9finger (2018/01) @karismann (2019/03) @Zomzog (2019/04) |
jimschubert
commented
Sep 11, 2019
This will break the JavaSpring templates… for example: Maybe a good way around this, since the template modified in this PR is used by multiple library options which apparently provide their own build scripts… would be to fully qualify the occurrences of JsonNullable (change @cbornet does that seem like a valid fix to get the import out of the shared template? For anyone affected by this in an already released version, you can create a new directory with a single file called During generation, pass the new folder to the template directory option for your tool:
The generator should fall back to embedded templates for any not found in the target directory. |
mateusz-nalepa
commented
Feb 13, 2020
Hi @jimschubert , What about solution like this? |
|
jimschubert
commented
Aug 31, 2020
Following up for visibility…
This would be an excellent option, and users can do this for any version of the tool by extending the templates. Since this PR would be a breaking change and that hasn't been addressed, I think we'll move forward with #6154 as this would accomplish the same while also moving us toward more vanilla output by default (without the JSON Nullable library). |
jimschubert
commented
Sep 21, 2020
Thanks again for the PR. We've merged #6154 so the issue should be addressed in a way that allows for both scenarios. |
closes#2901