Invalid check in router/url_tree/parseParens

Which @angular/* package(s) are the source of the bug?

router

Is this a regression?

No

Description

The parseParens method in url_tree.ts has a sanity check that checks if segment group is properly closed or not.

Lines 711 to 718 in c22b5ac

    
           // if is is not one of these characters, then the segment was unescaped 
        
           // or the group was not closed 
        
           if (next !== '/' && next !== ')' && next !== ';') { 
        
             throw new RuntimeError( 
        
               RuntimeErrorCode.UNPARSABLE_URL, 
        
               (typeof ngDevMode === 'undefined' || ngDevMode) && `Cannot parse url '${this.url}'`, 
        
             ); 
        
           }

This check does not pass when the segment group is defining an outlet with a path and children. For example:

/Home(app:Welcome//dock:left(1:One;pinned//2:Two;below=1//3:Three;pinned;above=2//4:Four))

In this case, after matching the outlet and its segments (dock:left), the next character is a ( to specify the children.

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

No response

Please provide the environment you discovered this bug in (run `ng version`)

No response

Anything else?

No response

fix(router): allow parsing url with outlet and children

How did you come about getting this URL in the first place? From my observations, an aux outlet with additional outlets alongside the primary will still generate a URL like dock:/(left//1:One...) and not dock:left(1:One)

fix(router): handle parenthesized outlets without a name in DefaultUr…

How did you come about getting this URL in the first place? From my observations, an aux outlet with additional outlets alongside the primary will still generate a URL like dock:/(left//1:One...) and not dock:left(1:One)

I know, just reading the code... 😄
Thanks for fixing it, and relieving my OCD.

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.}

Navigation Menu

Repository navigation

Invalid check in router/url_tree/parseParens #58516

Which @angular/* package(s) are the source of the bug?

Is this a regression?

Description

Please provide a link to a minimal reproduction of the bug

Please provide the exception or error you saw

Please provide the environment you discovered this bug in (run `ng version`)

Anything else?

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	// if is is not one of these characters, then the segment was unescaped
	// or the group was not closed
	if (next !== '/' && next !== ')' && next !== ';') {
	throw new RuntimeError(
	RuntimeErrorCode.UNPARSABLE_URL,
	(typeof ngDevMode === 'undefined' \|\| ngDevMode) && `Cannot parse url '${this.url}'`,
	);
	}

Invalid check in router/url_tree/parseParens #58516

Description

Which @angular/* package(s) are the source of the bug?

Is this a regression?

Description

Please provide a link to a minimal reproduction of the bug

Please provide the exception or error you saw

Please provide the environment you discovered this bug in (run ng version)

Anything else?

Activity

atscott commented on Oct 17, 2025

abdes commented on Oct 24, 2025

angular-automatic-lock-bot commented on Nov 24, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Please provide the environment you discovered this bug in (run `ng version`)