Fix(RequestMethod): Any interface HTTP Request method verification

[Hcreak]

对部分接口的HTTP请求方式进行校验 不正确的请求方式将被阻止并给出ERR_METHOD_INVALID错误信息

[iGeeky]

@Hcreak I think using exceptions to implement such checks might make the code a bit cleaner. This requires the following steps:

1. Define an exception under the errors package, for example: MethodInvalidError
2. Define the method check function in basic-service. checkMethod(method), which throws an exception if it does not match.
3. handle the exception in middlewares.error-cache.
4. call this.checkMethod('GET') in the function that needs to check the method.

In addition, you need to submit the corresponding unit test at the same time. To ensure that the newly added code is covered by the unit tests.

Doing this, in terms of performance, may not be the best, but it will make the code in the business method more simple.Often a single line of code is all that is needed to complete the check.
It also makes it easier to write unit tests: the current approach requires a method check failure in each business function to cover the branch where the check failed. With exceptions, you usually only need to write one check failure case.

[Hcreak]

@iGeeky

3. handle the exception in middlewares.error-cache.

I don't understand this place，
I maybe not find you have used this middleware in your code.

[iGeeky]

@Hcreak
I'm sorry, I made a typo. It should be middlewares/error-catch.
The location to use it is: https://github.com/iGeeky/wolf/blob/master/server/app.js#L39

[iGeeky]

When you modify the code, you need to execute the unit tests completely and make sure that all cases pass.
For a complete test, use the command: cd wolf/server && npm run test
To test a single module: cd wolf/server && mocha --exit test/20.user.test.js
In addition, you need to add test cases for the newly added code. Please refer to the code under wolf/server/test.

[iGeeky]

You don't need async here, right?

[Hcreak]

Yes.It does not need to be asynchronous. Sorry I have not finished.

[iGeeky]

@Hcreak After you change the response code to 400, many test cases will need to change the expected status code to 400. Make sure that all test cases pass.

[Hcreak]

@iGeeky All unit tests have passed :-)