queryParamsHandling: 'merge' behavior not matching documentation

🐞 bug report

Description

The documentation for the queryParamsHandling prop doesn’t seem to match the behavior when using queryParamsHandling: 'merge' inside of a router.navigate(...) call.

Instead of appending an additional instance of a particular queryParam, the navigation replaces the existing param, leaving the URL as /someRoute?page=2 instead of /someRoute?page=1&page=2 as the documentation seems to imply.

🔬 Minimal Reproduction

https://stackblitz.com/edit/angular-dqgg24

🌍 Your Environment

Angular Version:

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.800.1
@angular-devkit/build-angular     0.800.1
@angular-devkit/build-optimizer   0.800.1
@angular-devkit/build-webpack     0.800.1
@angular-devkit/core              8.0.1
@angular-devkit/schematics        8.0.1
@angular/cli                      8.0.1
@ngtools/webpack                  8.0.1
@schematics/angular               8.0.1
@schematics/update                0.800.1
rxjs                              6.5.2
typescript                        3.4.5
webpack                           4.29.0

[atscott]

Closing as this appears to have been resolved by #37980. The documentation now has // from /view1?page=1 to/view2?page=1&otherKey=2

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}