minevalley / core-api Goto Github PK

The absence of the @return tag for the getBankAccount() method of the Registrant class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getBankAccount() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the replaceItemAfterCrafting() method of the RecipeItemBuilder class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the replaceItemAfterCrafting() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the getContents() method of the Packet class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getContents() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the getOwner() method of the Residence class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getOwner() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the getName() method of the Registrant class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getName() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @param tag for the listener parameter for the registerListeners() method of the Core class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the registerListeners() method by including the necessary @param tag for the listener parameter. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of @param tag for the powerConsumption parameter and @return tag for the setPowerConsumption() method of the RecipeBuilder class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the setPowerConsumption() method by including the necessary @param tag for the powerConsumption parameter and the @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The JavaDoc for the FixedPlayerInteractEvent class in the Core API contains an unexpected issue. There is a redundant </p> end tag that needs to be removed.

To resolve this, simply remove the extra </p> end tag and ensure that the JavaDoc for the FixedPlayerInteractEvent class is properly formatted. This correction will enhance the readability and correctness of the documentation.

Description

This is a suggestion to use dependabot or renovatebot on the Core-API repository. These tools can help automate the process of updating dependencies and keep the project up-to-date with the latest security patches and bug fixes.

Benefits

• Saves time and effort by automating dependency updates.
• Keeps the project up-to-date with the latest security patches and bug fixes.
• Helps maintain a healthy and secure codebase.

Proposed Solution

It is proposed that dependabot or renovatebot be used to manage dependencies on this repository. Both tools are widely used and have proven to be effective in keeping projects up-to-date with the latest dependencies.

Additional Information

• Dependabot
• Renovatebot

• remove current api version (why does it need to include that?)
• remove the latest change (maybe a changelog instead?)
• add some information how to install the api (jitpack or maven profile)

The absence of the @return tag for the getSign() method of the Residence class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getSign() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the getTarget() method of the Parcel class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getTarget() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @param tag for the parcel parameter for the deliverParcel() method of the Registrant class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the deliverParcel() method by including the necessary @param tag for the parcel parameter. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the participate() method of the Task class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the participate() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the asItem() method of the Parcel class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the asItem() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The JavaDoc for the getLocation() method contains malformed HTML. Specifically, the use of the & character is not in the correct HTML entity format.

To address this issue, it is recommended to replace the raw & with the appropriate HTML entity, such as &. This correction ensures proper rendering and compliance with HTML standards in the JavaDoc documentation.

HTML Malformed

[ERROR] D:\CodeHub\Core-API\src\main\java\minevalley\core\api\crafting\recipe\builder\RecipeBuilder.java:25: error: malformed HTML
[ERROR]      * If the recipe is marked as "setShapeless(true)" this list is used for <Slot, Item> detection
[ERROR]                                                                              ^
[ERROR] D:\CodeHub\Core-API\src\main\java\minevalley\core\api\crafting\recipe\builder\RecipeBuilder.java:25: error: bad use of '>'
[ERROR]      * If the recipe is marked as "setShapeless(true)" this list is used for <Slot, Item> detection
[ERROR]                                                                                         ^

The JavaDoc for the setIngredients() method contains malformed HTML. Specifically, the use of the < and > character is not in the correct HTML entity format.

To address this issue, it is recommended to replace the raw < and > with the appropriate HTML entity. This correction ensures proper rendering and compliance with HTML standards in the JavaDoc documentation.

Missing Tag

The absence of the @return tag for the setIngredients() method of the RecipeBuilder class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the setIngredients() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the setItem() method of the RecipeItemBuilder class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the setItem() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

should be added within one of the next updates:

performCommand(String command)

chat(String message)

chat(MessageType type, String message)

MessageType (enum):
NORMAL,
WHISPHER,
SHOUT,
FRACTION,
ACTION

The absence of the @param tag for the name parameter for the changeName() method of the Group class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the changeName() method by including the necessary @param tag for the name parameters This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the getSender() method of the Parcel class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getSender() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of @param tag for the block parameter and @return tag for the getAreaOfBlock() method of the Core class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getAreaOfBlock() method by including the necessary @param tag for the block parameter and the @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The JavaDoc for the createItem() method in the Core API contains an unexpected issue. There is a redundant </span> end tag that needs to be removed.

To resolve this, simply remove the extra </span> end tag and ensure that the JavaDoc for the createItem() method is properly formatted. This correction will enhance the readability and correctness of the documentation.

The JavaDoc for the getRecipeIngredients() method contains malformed HTML. Specifically, the use of the < and > character is not in the correct HTML entity format.

To address this issue, it is recommended to replace the raw < and > with the appropriate HTML entity. This correction ensures proper rendering and compliance with HTML standards in the JavaDoc documentation.

The absence of the @return tag for the getAmountInCents() method of the BankAccount class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getAmountInCents() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of @param tags for the cls and listener parameters for the unregisterEvent() method of the Core class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the unregisterEvent() method by including the necessary @param tags for the cls and listener parameters. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the getRemainingMinutes() method of the Parcel class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getRemainingMinutes() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the getPermissioned() method of the Residence class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getPermissioned() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of @param tags for the cls and listener parameters for the registerEvent() method of the Core class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the registerEvent() method by including the necessary @param tags for the cls and listener parameters. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the getStreet() method of the Residence class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getStreet() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of @param tag for the name parameter and @return tag for the setRecipeName() method of the RecipeBuilder class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the setRecipeName() method by including the necessary @param tag for the name parameter and the @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the getPages() method of the Letter class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getPages() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the getCroppedName() method of the Registrant class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getCroppedName() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the getRegion() method of the Residence class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getRegion() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the getAddress() method of the Registrant class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getAddress() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the getAdmins() method of the Residence class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getAdmins() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of @param tag for the output parameter and @return tag for the setOutputItem() method of the RecipeBuilder class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the setOutputItem() method by including the necessary @param tag for the output parameter and the @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the getLocation() method of the Residence class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getLocation() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the getId() method of the Residence class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getId() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the setIgnoreMetadata() method of the RecipeItemBuilder class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the setIgnoreMetadata() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @param tag for the name parameter for the setRecipeName() method of the Task class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the setRecipeName() method by including the necessary @param tag for the name parameter. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of @param tag for the user parameter and @return tag for the isPermissioned() method of the Residence class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the isPermissioned() method by including the necessary @param tag for the user parameter and the @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the addRequirement() method of the RecipeItemBuilder class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the addRequirement() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of @param tag for the listener parameter for the createFakeArmorStand() method of the Core class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the createFakeArmorStand() method by including the necessary @param tags for the listener parameter. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The JavaDoc for the convertColorCodes() method contains malformed HTML. Specifically, the use of the & and > character is not in the correct HTML entity format.

To address this issue, it is recommended to replace the raw & and > with the appropriate HTML entity, such as &. This correction ensures proper rendering and compliance with HTML standards in the JavaDoc documentation.

The absence of the @return tag for the getApartmentBlock() method of the Apartment class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getApartmentBlock() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the setShapeless() method of the RecipeBuilder class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the setShapeless() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the getMailbox() method of the Residence class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the getMailbox() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

The absence of the @return tag for the addMember() method of the Group class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the addMember() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.

HTML Malformed

[ERROR] D:\CodeHub\Core-API\src\main\java\minevalley\core\api\crafting\recipe\builder\RecipeBuilder.java:33: error: malformed HTML
[ERROR]      * If the recipe is marked as "setShapeless(true)" this list is used for <Slot, Item> detection
[ERROR]                                                                              ^
[ERROR] D:\CodeHub\Core-API\src\main\java\minevalley\core\api\crafting\recipe\builder\RecipeBuilder.java:33: error: bad use of '>'
[ERROR]      * If the recipe is marked as "setShapeless(true)" this list is used for <Slot, Item> detection
[ERROR]                                                                                         ^

The JavaDoc for the addIngredients() method contains malformed HTML. Specifically, the use of the < and > character is not in the correct HTML entity format.

To address this issue, it is recommended to replace the raw < and > with the appropriate HTML entity. This correction ensures proper rendering and compliance with HTML standards in the JavaDoc documentation.

Missing Tag

The absence of the @return tag for the addIngredients() method of the RecipeBuilder class is causing a significant issue. This omission is breaking the JavaDoc generation process during the build.

To resolve this issue, update the JavaDoc for the addIngredients() method by including the necessary @return tag. This will not only fix the JavaDoc generation problem but also ensure that developers have essential information about the method's parameters.