-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
added action and state sanitizer to store dev tool #494 #516
Conversation
Hey @roopkt, this PR and #517 is more involved than just adding a key to the config object. You'll need to pass the config options to the extension itself when sending messages. |
Sure I will update , thanks! |
Finished passing state and action sanitizer to devtools. Fixes #494 |
I'm not sure that you updated the pull request with your latest changes. |
Hi @aboyton I am not sure how to update the pull request. I am going to create another local branch and try to check in again with putting the Pull Request number #516 in the comment hope that will update the pull request. If that is incorrect, please guide me how to update this pull request with my latest changes? Also I am not able to take the latest from the upstream ngrx/platform branch therefore every time I check in I get a merge issue.
My upstream is https://github.com/ngrx/platform.git and above command gives me below error. Therefore I have to do manual merge I go a literally take the copy of ngrx/platform code and merge locally in my vsCode. Please suggest is there any better way to take latest from upstream to my local forked branch ?
|
I'm no expert at this, but I generally follow the advice that's from this answer. https://stackoverflow.com/questions/25545613/how-can-i-push-to-my-fork-from-a-clone-of-the-original-repo First I'd set a new remote called
Then you can push your changes to your new remote with The pull request should then automatically update with the latest changes. You shouldn't need to pull from master for making this diff, but if you wanted to personally I'd do |
The options should be passed to the extension. Adding them to the config isn't enough |
Hey @brandonroberts , |
Are your most recent changes in the branch |
Hey @aboyton |
I don't know a way of changing your pull request to compare against a different branch. It's probably simplest to go to https://github.com/roopkt/platform/tree/devtool-sanitizers and create a new pull request. |
Closed in favor of #544 |
Please merge this changes which supports action and state sanitizer to the store dev tool. Let me know if there is any improvement required.