Issue with having multiple --base-href option. (Data path “.baseHref” should be string.)

[chaitanyamullangi]

Bug Report or Feature Request (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)

- [ ] new
- [x] build
- [x] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [x] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

node -> v8.11.3
npm -> v5.5.1
ng -> v6.2.7

Repro steps

I have recently upgraded to Angular 6 from Angular 5. I am having Angular-cli@6.2.7
In my package.json, I have configured script "build": "ng build --prod --base-href=/my-ui/"
now when I run yarn build --base-href=/my-ui-2/. resulting following error

The log given by the failure

$ng build --prod --base-href=/my-ui/ --base-href=/my-ui-2/
Schema validation failed with the following errors:
  Data path ".baseHref" should be string.
error Command failed with exit code 1.

Desired functionality

It used to work in earlier versions of angular-cli considering the last option i.e my-ui-2.

Mention any other details that might be useful

[alan-agius4]

Hi, I have looked at this and it seems that is no longer reproducible in version 7 of the CLI.

[clydin]

I think there is still an open concern here regarding the behavior in the case an option is specified two or more times. Should it error? Warn? Which of the options should be used? etc.

[chaitanyamullangi]

In the case an option is specified two or more times. In earlier versions it used to pick the last option. which is the expected as well.

[dominikg]

I reported a similar issue here: #11448
and agree with @mcshiva that the behavior (last value is used when an option is passed multiple times) is expected.

[clydin]

I think I’d still prefer some type of warning though. Depending on the setup, it may not be obvious that multiple values are being passed.

[hansl]

The latest v7 argument parser picks the last option. I think it was in the way yargs-parser was in v6. This issue is fixed. What remained is whether or not we should show some warning, and I think that's a generally good idea.

[angular-automatic-lock-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.}