I would like to. Unfortunately the people (and the original project) are on github, so cutting that off is nothing short of killing this project in the crib
I in fact do have a GitLab account, but I decided to only work on GitHub... Switching to GitLab could definitely starve the Project of potential users which report issues or even contribute.
I feel like GitHub also seems to be a bit easier on users and maybe even a bit less overwhelming than GitLab. As @The-EDev already mentioned, GitHub is where most people are at.
So this happened :)
(I also fixed the matrix avatar problem but that's not as big a deal)
Awesome. 🎉 Congrats. ☺️
@luca-schlecker let me know if you need help with CrowCpp/Crow#258, I'm currently focusing on expanding the documentation but once that's done I think I can focus on async work. If we can squeeze Async handlers in the next release I believe I would confidently call it v1.0
Taking on CrowCpp/Crow#25 once more. This time I'm going through the original repo changes since August 2014 and trying to integrate those into Crow's parser
I don't blame the people at nodejs for dropping the parser XD
Yes, I was setting up a plan on where to take the parser and needed to know whether there was a chance that crow could become a client
My plan is 3 stages, the first is to get the code up to date with the latest nodejs parser (only 6 years of updates to implement, the purpose behind that is to make sure we're on solid ground before moving forward). Then strip not needed code (response parsing and client related code), and then slowly change parts to be more in tune with Nginx's parser (so we can ultimately make the change to the latter which is still maintained)