Closed mrahhal closed 8 years ago
Hey @Daniel15 I'm actually failing to build RouteJs locally (except for RouteJs.AspNet), there is a SharedAssemblyVersionInfo.cs
included in all of the projects excluding RouteJs.AspNet. But this is nowhere to be found and it's resulting in a build error, what's going on?
According to the projects, it should be in src
right next to SharedAssemblyInfo.cs
.
One thing I noticed, it might have been better to just keep everything in the javascript side (convert as necessary when building the routes in js). I didn't know we'll need to do something in js when I started writing LowerCaseRouteProcessor
. But is it really worth it now that we have everything working? I don't mind rewriting the pieces (it will actually be easier) in js if you think that's better than having a new interface (IRouteProcessor
) to manage.
So this was really awkward, turns out we could do everything so much easier in javascript. Also, we don't care for case inside param values (I didn't know that). So the result is that we can do everything from js and in so much less code (no need for IRouteProcessor
or pretty much everything else on the server anymore).
I'm happy with what we have here, so unless you have something to change I think this is done. I tested using the dev package.
there is a SharedAssemblyVersionInfo.cs included in all of the projects excluding RouteJs.AspNet. But this is nowhere to be found and it's resulting in a build error, what's going on?
Running build-dev.bat will create that file.
Thanks! This looks pretty good. Just a few small comments (inline). Doing the lowercasing in JS does look a lot simpler :)
Right, doing those now.
This looks good to me, thanks! Is this ready to merge? If so, can you please squash your commits?
Yes this is squashed and ready. Didn't have the time to test this with AspNet 5 though.
lowerCaseUrls
unrecognized in web.configFixes #45