My presumption is that there should be a way to do this automatically as part of the release process.

I'm not 100% how best to achieve this, so before running with it I'd like to open it out for discussion.

To start things off, this SO question has a few answers/suggestions.

One suggestio

We should start using https://github.com/all-contributors/all-contributors to fully recognize the people who contribute to this project, both with code and via answering questions.

Many project docs websites want to show the "Fork me on github" type banner. An Orchid component should be able to add that banner to any theme. It should be added to the OrchidGithub plugin.

Features:

• Support both classic and modern styles (use modern by default)
• Component configura

Prerequisites

• If this is a question/suggestion, I have already considered discuss it on Discord Server
• This issue specifically has something to do with Twitch4J
• I have attempted to [look for similar issue

The "add scopes" link points to #Usage, which is not present. I suppose it should lead to #usage-in-zalandos-stups-environment or not be a link at all.

Actually is possible to manage the public chat formatting setting

• [factionrole factioname] playername

But that is not available for truce/ally/faction chat where is not possible to format the [factionrole factioname] with different color because factionrole/factioname/playername is handled by %s

"factionChatFormat": "§a§lFactionChat §a%s§8: §a%s",
"allianceChatFormat": "§d§lAllyCh

javacOptions in unidoc are passed as options to javadoc

If javacOptions in unidoc contains options like -target 1.8, javadoc will fail because -target is not a valid option to javadoc.

S

Expected Behavior

Each class should have it's own unit test

Actual Behavior

Not every class has it's own unit test

Steps to Reproduce the Problem

1. Look at the sources in src/main/java
2. Look for the same source file in src/test/java with Test appended to its name

Specifications

• n/a

I have a package structure which has scala files but provides Java API as well.
But everything is written in scala. I am using genJavaDoc to generate java documentation. It does get generated for scala classes but package documentation does not get generated for javadoc.

I jave followinf package structure:
com.example.javadsl

• javadsl.scala
• ILocationService.scala

javadsl.scala look

Relationships from an outer class to an inner class are not shown on the diagrams. Add them to improve navigation between classes.

For now, the class name provided in Link elements is taken directly from the Javadoc's text. This is barely usable to actually find the corresponding class/method.
It would be nice to find a way to actually read the corresponding fully qualified class name from the imports, so that we can provide the actual Class<?>/Method object at runtime.

Sometimes, developers write useless javadocs such as the example below

/**
 * Some Foo Method.
 * @param id the id
 * @return 
*/
int someFooMethod(int id){ return 0; }

The plugin should spot this kind of "documentation" and present them into the report.
A common pattern to detect such useless javadocs are:

• the method documentation includes only the name of the method,