Specificity failure with multiple parameter nodes #1

Closed
opened 2024-09-07 17:39:04 -05:00 by Sky · 1 comment
Owner

When there is more than one parameter node under a single node, specificity can be a problem; which parameter node is the correct one? The current idea for a solution is to look ahead by one node.

When there is more than one parameter node under a single node, specificity can be a problem; which parameter node is the correct one? The current idea for a solution is to look ahead by one node.
Author
Owner

Actually, will try to homogenize the parameter nodes as a single node (perhaps :x?), which may even save memory and iterations

Actually, will try to homogenize the parameter nodes as a single node (perhaps :x?), which may even save memory and iterations
Sky closed this issue 2024-09-07 22:35:44 -05:00
Sky added the
bug
label 2024-09-07 22:36:07 -05:00
Sky self-assigned this 2024-09-07 22:36:10 -05:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: PHP/Router#1
No description provided.