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
I debugged it, it ends up being in ngtools_impl.js which is in angular until v4.4.x and disappears in v5. So still have to check whether v5 is also affected.
problem is following in Routedef:
RouteDef.fromString = function (entry) {
var split = entry.split('#');
return new RouteDef(split[0], split[1] || null);
};
it gets passed e.g. "c:/projects/angular/c#notes/notes/src/app/app.module#AppModule", and the split() on # takes the wrong parts of the string.
Following fixes it (it takes the part after the most right # and the whole part in front):
RouteDef.fromString = function (entry) {
var split = entry.split('#');
return new RouteDef(split.slice(0, -1).join('#'), split.pop() || null);
};
Activity
sboden commentedon Oct 24, 2017
You have a directory "C#Notes" ... remove the #.
filipesilva commentedon Oct 25, 2017
@sboden is right that this is caused by the
#character, but we should fix this on our side as it is due to file resolving logic in Angular.sboden commentedon Oct 25, 2017
I agree the code should be fixed... short-term work around would be to remove # from the directory name.
If this issue is fixed, issue #8118 will also be fixed I think.
sboden commentedon Oct 25, 2017
I debugged it, it ends up being in ngtools_impl.js which is in angular until v4.4.x and disappears in v5. So still have to check whether v5 is also affected.
problem is following in Routedef:
it gets passed e.g. "c:/projects/angular/c#notes/notes/src/app/app.module#AppModule", and the split() on # takes the wrong parts of the string.
Following fixes it (it takes the part after the most right # and the whole part in front):
angular-automatic-lock-bot commentedon Sep 7, 2019
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.