allow javadoc comments before and after enum values

[nomuna]

Fix #15185

---

Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green
• Tests are added where necessary
• The JDL part is updated if necessary
• jhipster-online is updated if necessary
• Documentation is added/updated where necessary
• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

When you are still working on the PR, consider converting it to Draft (bellow reviewers) and adding skip-ci label, you can still see CI build result at your branch.

[MathieuAA]

LGTM, I have one question: do you want the comments to appear in the generated files as well?
If that's the case, then a bit more work is needed.

[nomuna]

@MathieuAA As far as the description of this bug goes the issue is that the parser is causing an issue
since the grammar doesn't allow comments next to the enum values. There is no information if they want it in the
generated java code.

They are right that it was documented as possible but not really working.

Current state is that even the comments on enum itself is also not carried over to the java code.

/** This comment will be taken into account */
enum Country {
  // But not this one!
  FRANCE
}

As I understood in this issue, there is no information if they want the comments to be in the generated java classes. So as for this specific case the PR is complete, I think?

In #14869 they want it in the swagger info. I am not even sure if it is doable. So I guess my PR only solves the
parser issue for #14869. So may be I should update my PR to remove the 'Fix #14869' from the comment.

Example from #14869

enum myEnum { V1 /** value1 */, V2 /**value2 */, V3 }

Their example doesn't contain a javadoc for V3. As a rule for javadoc the comment should precede the enum keys but they
write it in the back which makes me think we should may be just allow javadoc in front of an enum key.

[MathieuAA]

@nomuna great, thanks!

[MathieuAA]

In #14869 they want it in the swagger info. I am not even sure if it is doable. So I guess my PR only solves the
parser issue for #14869. So may be I should update my PR to remove the 'Fix #14869' from the comment.

it would be a good idea :)

[nomuna]

Hi @MathieuAA,

do you have a write access? Are you supposed to merge it or should I request for someone in the jhipster chat?

Have a nice day.