-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modular code needed #2
Comments
I am willing to take up this issue. I have another suggestion regarding the code modularity. Currently the controller functions for each of the routes are written right inside the route definition. Example: router.get("/", function (req, res, next) {
request(
"https://www.gogoanime1.com/search/topSearch?q=" + req.query.q,
(error, response, html) => {
res.send(response.body);
}
);
}); A good convention to follow is to create a controllers/ directory and have all these controller functions (let's call the above handler function as topSearchHandler) in there so that the api end point just has to call the function:
|
Yeah sounds reasonable, can you create an issue for this as well so that we don't forget the main aim if this issue. |
Thank you. I'll do that. Also, there a typo in the issue label |
Yeah Removed |
There is a need of making the code modular.
like putting all the anime streaming route in one folder, loader in one folder and manga reader in one folder
The text was updated successfully, but these errors were encountered: