Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ongoing Minor Issue List SpongeDocs Edition #698

Open
Inscrutable opened this issue Jun 2, 2018 · 12 comments
Open

Ongoing Minor Issue List SpongeDocs Edition #698

Inscrutable opened this issue Jun 2, 2018 · 12 comments
Labels
input wanted We would like to hear your opinion

Comments

@Inscrutable
Copy link
Member

Rather than push trivial fixes as PRs, we prefer to collect them together and push them in batches.
Please let us know of any minor corrections, nitpicks, and errors in spelling, grammar or punctuation that are needed, and we shall do our best to see they are dealt with.

This is a reincarnation of the humungous list at #437 - thanks to everyone so far!

@Inscrutable Inscrutable added the input wanted We would like to hear your opinion label Jun 2, 2018
@ST-DDT
Copy link
Member

ST-DDT commented Jul 9, 2018

Exploits Patched implemented in Sponge

Should be

Exploit Patches Implemented In Sponge

or

Exploits Patched In Sponge

@ST-DDT
Copy link
Member

ST-DDT commented Jul 29, 2018

If a command has child commands, a :javadoc:CommandExecutor, set through
:javadoc:CommandSpec.Builder#executor(CommandExecutor) and their associated
:javadoc:CommandSpec.Builder#arguments(CommandElement) are optional. The behavior of error in selection and
argument parsing of child commands is dependent on whether this parent executor exists.

This section is hard to understand

@ST-DDT
Copy link
Member

ST-DDT commented Aug 31, 2018

public List<String> getSuggestions(CommandSource source, String arguments) throws CommandException {

This method is now defined like this:

public List<String> getSuggestions(CommandSource source, String arguments, @Nullable Location<World> targetPosition) throws CommandException {

@ST-DDT
Copy link
Member

ST-DDT commented Aug 31, 2018

try (StackFrame frame = Sponge.getCauseStackManager().pushStackFrame()) {

Should be

try (StackFrame frame = Sponge.getCauseStackManager().pushCauseFrame()) {

@ST-DDT
Copy link
Member

ST-DDT commented Aug 31, 2018

  • Differently named references to PluginContainers / Plugins

  • plugin

  • myplugin

  • yourPluginInstance

Should probably use plugin all the time.

@Grauldon
Copy link
Contributor

Grauldon commented Feb 9, 2019

  • Under Tasks -> Build, click on jar
    should be
  • Under Tasks -> Build, double- click on jar

@Grauldon
Copy link
Contributor

Grauldon commented Mar 10, 2019

  • Update Ore entry in Sponge Glossary to just The Official Sponge plugin hosting site. (Could provide a link to the site.)

@Grauldon
Copy link
Contributor

Grauldon commented May 5, 2019

  • Locate and update branch names from stable and bleeding to api-# as appropriate.

@phit phit pinned this issue Jun 4, 2019
@Inscrutable
Copy link
Member Author

Good catch. That's another issue caused by a title leading with a number and fooling the ReST / Sphinx formatting. We edited out the last few, and this one got missed somehow.

@ST-DDT
Copy link
Member

ST-DDT commented Jun 15, 2019

screenshot

It looks like it is meant to say "Table of Contents"

Originally reported by 3TUSK on Discord

@mjra007
Copy link

mjra007 commented Sep 15, 2020

This was pointed out originally on discord. There is a very minor "issue" with a code block to access a data manipulator for a block.

import org.spongepowered.api.data.key.Keys;
import org.spongepowered.api.data.manipulator.mutable.block.DirectionalData;

public boolean isFacingNorth(Location<World> blockLoc) {
    Optional<DirectionalData> optionalData = blockLoc.get(DirectionalData.class);
    if (!optionalData.isPresent()) {
        return false;
    }
    DirectionalData data = optionalData.get();
    if (data.get(Keys.DIRECTION).get().equals(Direction.NORTH)) {
        return true;
    }
    return false;
}

It might be that the code gets optimized after it is compiled, especially the last if statement (don't know). However, this could be easily be written like this:

import org.spongepowered.api.data.key.Keys;
import org.spongepowered.api.data.manipulator.mutable.block.DirectionalData;

public boolean isFacingNorth(Location<World> blockLoc) {
    return blockLoc.get(DirectionalData.class)
            .filter(dir -> dir.direction().get().equals(Direction.NORTH))
            .isPresent();
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
input wanted We would like to hear your opinion
Projects
None yet
Development

No branches or pull requests

5 participants