slove code issue

[visonforcoding]

This request solves 2 problems
First, prevent unlimited generation of temporary class files. Ensure that one source code file corresponds to one generated file.
Secondly, 1 bug was solved.
When the method of the source code is bound, there is a Declaration error when the parameter is added or modified.
@RequestMapping is bound with aop.

    /**
     * @RequestMapping(name="test",path="/test",method="GET")
     */
    public function test()
    {
        return 'hello,hll1';
    }

    /**
     * @RequestMapping(name="add",path="/add",method="GET")
     * @LoginRequired
     */
    public function add4343(GoodsQuery $goodsQuery)
    {
        return 'hello,add';
    }

The corresponding file generated is Mall_Api_Controller_IndexCtrller_2956060156.php

Change the source code to

   /**
      * @RequestMapping(name="test",path="/test",method="GET")
      */
     public function test()
     {
         return'hello,hll1';
     }

     /**
      * @RequestMapping(name="test",path="/add",method="GET")
      * @LoginRequired
      */
     public function add4343()
     {
         return'hello,add';
     }

No new files will be generated.

We will get error

Declaration of Mall\Api\Controller\IndexCtrller_2956060156::add4343(Mall\Api\Controller\RequestMapper\GoodsQuery $goodsQuery) should be compatible with Mall\Api\Controller\IndexCtrller::add4343()

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[koriym]

@visonforcoding Thanks for the PR. Please refer https://github.com/ray-di/Ray.Aop/blob/2.x/.github/CONTRIBUTING.md .

[koriym]

-       $aopClassName = ($this->aopClassName)($class, $bind->toString(''));
-       $classReflection = new ReflectionClass($class);
+       $aopClassName = sprintf('%s_%s', $class, filemtime($classReflection->getFileName()));

It detects changes in the source code, but not changes in the bindings.

[koriym]

I create the issue #182

[koriym]

I checked again.

If class generation for different bindings is done at the same runtime, this PR will cause problems. Sure it is a rare case, but compatibility is destroyed. Adding a file stamp to the current binding solves this problem.

Once generated, the class is checked for existence and will not be generated again.

[koriym]

@visonforcoding Will fix with #192