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

refactor(store): rename mapToAction operator to act #1927

Merged
merged 2 commits into from
Jun 6, 2019
Merged

refactor(store): rename mapToAction operator to act #1927

merged 2 commits into from
Jun 6, 2019

Conversation

alex-okrushko
Copy link
Member

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Closes #1907

What is the new behavior?

Does this PR introduce a breaking change?

Anyone who started using mapToAction already would have to rename it act

[x] Yes
[ ] No

Other information

@ngrxbot
Copy link
Collaborator

ngrxbot commented Jun 6, 2019

Preview docs changes for 35197c4 at https://previews.ngrx.io/pr1927-35197c4/

@brandonroberts brandonroberts merged commit 36f14bd into ngrx:master Jun 6, 2019
@alex-okrushko alex-okrushko deleted the act branch October 30, 2019 03:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

RFC: Hold back on releasing mapToAction
4 participants