Closed phroa closed 8 years ago
GroundLumanceProperty
is misspelled (should be GroundLuminanceProperty
), and LightEmissionProperty
is inconsistently named (it would make more sense to call it LuminanceProperty
to match GroundLuminanceProperty
and SkyLuminanceProperty
.
Also, there should probably be a HumidityProperty
for Location
s.
fro
instead of for
in ExperienceHolderData
ImmutableDataManipulator
in ImmutableCareerDataInventory.slots()
should have a signature of <T extends Slot> Iterable<T> slots();
because it always returns Slots
.
@Mumfrey Location
and Transform
use setXXX
methods for creating new instances with modified data.
BlockSnapshot
uses withXXX
methods. As these methods don't set something but create a new instance, withXXX
seems more appropriate here. Needs to be renamed.Keys
- missing ACHIEVEMENTS
key+ public static final Key<SetValue<Achievement>> ACHIEVEMENTS = null;
ImmutableAchievementData
- typo- ImmutableSetValue<Achievement> achiements();
+ ImmutableSetValue<Achievement> achievements();
I can create a PR for this as well, but I consider this a too small/OCD change. Compare/Merge
PersistingData
- typo- Value<Boolean> perists();
+ Value<Boolean> persists();
Inventory.slots() should have a signature of
Iterable slots(); because it always returns Slots. @Mumfrey
As mentioned here this is a big fat no:
Leaf nodes are currently guaranteed to be Slots but I definitely don't want this encoded in the API, because the entire point of this is that it can support future changes in minecraft's inventory system. This is why pretty much all generic signatures are
, because the contract is designed around the core premise that you deal with Inventorys not any particular sub interface.
- Mumfrey 2015
#wasSpawnSet()
into #isSpawnSet()
in the JavaDocsSPAWNER_REQURED_PLAYER_RANGE - typo
I already fixed that in #860.
That was also already fixed in my PR.
@bloodmc Might need discussion, but things related to BlockTrait
values (like getTraitMap
) should return ? extends Comparable
since all values are Comparable
.
For example:
// Current
Map<BlockTrait<?>, ?> getTraitMap();
// Proposed
Map<BlockTrait<?>, ? extends Comparable<?>> getTraitMap();
// or
Map<BlockTrait<?>, Comparable<?>> getTraitMap();
(Fixed)Inventory.poll()
returns ItemStack
, but the javadoc claims it can return Optional.empty()
! link to relevant line
@phroa mind updating the issue description of the various OCD things listed here?
@ryantheleach I think only one would be needed - the value of one is simply the opposite of the other.
Keys.EXPLOSIVE_RADIUS
, ExplosiveRadiusData
and Explosive
are inconsistent in whether the explosive radius is a Value<Integer>
or a MutableBoundedValue<Integer>
. Should be the latter because negative radius makes no sense.ImmutableFlamableData
is misspelled@ryantheleach feature requests aren't minor changes, those should be an issue.
Creating a new OCD list for beta See #1000
Any still unresolved issues from here that I may have missed should be reported there.
@saladoc remake your concern as an issue as well
https://github.com/SpongePowered/SpongeAPI/blob/master/src/main/java/org/spongepowered/api/entity/EntityTypes.java#L64 shouldn't it be ZOMBIE_PIGMAN
instead of PIG_ZOMBIE
?
Track at https://github.com/SpongePowered/SpongeAPI/pull/860
Minor Issues List
Direction:30
GameMode
javadoc uses fully qualified link toPlayer
Some method declarations inappears to have been refactored so I won't touchDataHolder
are generic although they don't have to. This leads to worse usability / more raw casts. See comment: https://github.com/SpongePowered/SpongeAPI/issues/221#issuecomment-107156044AbstractInventoryProperty
could extendAbstractProperty
. See comment: https://github.com/SpongePowered/SpongeAPI/issues/221#issuecomment-119275472 for moreCheckstyle warnings