feat(signals): add prepend option to addEntity #4721
+98
−9
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The addEntity function in @ngrx/signals currently appends new entities to the end of the entities array by default. There is no way to control the insertion order, limiting flexibility in scenarios where entities need to be added at the beginning (e.g., for "most recent first" displays).
Closes # (No specific issue linked; this is a general enhancement based on potential community needs.)
What is the new behavior?
This PR adds an optional prepend?: boolean parameter to the addEntity function. When prepend: true is specified, the new entity is inserted at the beginning of the entities array instead of being appended to the end. If prepend is omitted or set to false, the existing behavior (appending to the end) is preserved.
Example
Does this PR introduce a breaking change?