Relative path fixes needed

[brandonferens]

The imports method in the abstract enum generator is prone to bugs. The method attempts to figure out where the custom methods exist and where the abstract enum exists and the relative path between the two so that the imported custom methods are handled correctly.

Given the following two paths:

• resources/js/enums
• resources/js/vendor/paragon/enums

It will determine the relative path is ../vendor/paragon/enums which is what we want.

The issue is this. After it determines the closest parent directory, in the above case js/ it starts determining if it should use .. as the path, or a directory name. If a directory name happens to be the same further down in the child directories it will get replaced with ... For example:

• resources/js/enums/paragon
• resources/js/vendor/paragon/enums

This would result in the path ../vendor/../enums as the fourth directory in each are the same.