You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I encountered some issues while learning the code. If my understanding is incorrect, I apologize in advance for the trouble. In the insertChild() method of the tree.go file, in the processing branch of the parameter node (param), when there are subpaths after the wildcard, the code creates a new child node but does not update the indices. Moreover, it seems that all the generated child nodes after entering this method have the same fullpath.
// if the path doesn't end with the wildcard, then there
// will be another subpath starting with '/'
if len(wildcard) < len(path) {
path = path[len(wildcard):]
child := &node{
priority: 1,
fullPath: fullPath,
}
n.addChild(child)
n = child
continue
}
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I encountered some issues while learning the code. If my understanding is incorrect, I apologize in advance for the trouble. In the insertChild() method of the tree.go file, in the processing branch of the parameter node (param), when there are subpaths after the wildcard, the code creates a new child node but does not update the indices. Moreover, it seems that all the generated child nodes after entering this method have the same fullpath.
Beta Was this translation helpful? Give feedback.
All reactions