Skip to content

fix(@angular-devkit/build-angular): error when both baseUrl and devServerTarget are used in protractor #13614

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

Merged
merged 3 commits into from
Feb 9, 2019
Merged

Conversation

alan-agius4
Copy link
Collaborator

fix(@angular-devkit/build-angular): error when both baseUrl and devServerTarget are used in protractor

Users cannot use both baseUrl and devServerTarget, and the later superseeds the baseUrl.

Fixes #13611

@alan-agius4 alan-agius4 added the target: patch This PR is targeted for the next patch release label Feb 7, 2019
@@ -81,7 +85,7 @@ export class ProtractorBuilder implements Builder<ProtractorBuilderOptions> {
}

// Compute baseUrl from devServerOptions.
if (options.devServerTarget && builderConfig.options.publicHost) {
if (builderConfig.options.publicHost) {
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This method is never called when options.devServerTarget is falsy

concatMap(() => options.devServerTarget ? this._startDevServer(options) : of(null)),

@alan-agius4 alan-agius4 added the needs: discussion On the agenda for team meeting to determine next steps label Feb 7, 2019
@mgechev mgechev removed the needs: discussion On the agenda for team meeting to determine next steps label Feb 7, 2019
Alan added 2 commits February 8, 2019 07:53
…vServerTarget` are used in protractor

Users cannot use both baseUrl and devServerTarget, and the later superseeds the baseUrl.

Fixes #13611
Users should use baseUrl property in the Protractor config file
@alan-agius4
Copy link
Collaborator Author

@filipesilva, PR updated following the team meeting

I left the error message, as it's best to error out rather than have undefined behaviour, for the time being until this option is removed.

Copy link
Contributor

@filipesilva filipesilva left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@clydin PTAL as well.

@alexeagle alexeagle merged commit 5415bcc into angular:master Feb 9, 2019
@alan-agius4 alan-agius4 deleted the e2e-error-baseurl branch February 9, 2019 12:00
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

--base-url has no effect
6 participants