Added addAndReturn for easier Component Manipulation #222
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes it is useful to return the Component instead of the Entity. Especially when using the Pooled Engine.
With the PooledEngine you can't use the Constructor of a Component to init its values. The Current API forces you to Keep a reference for every Component when you want to modify data in it when adding a new Entity.
This PR introduces the
addAndReturn(Compoment component)
Method so you can write something like that:entity.addAndReturn(pooledEngine.createComponent(ComponentA.class)).set(data1, data2)
Where
set()
is a method that sets the data of the component. That is much more convenient thanEspecially when dealing with a lot of components.
I also added a unitTest case for that Method which passes. It also won't break existing API behaviour.