WIP: Use methods of utility class as extensions #653
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Copied from the documentation:
In some cases, a utility class with methods for a specific object already exists. However, since these methods are not annotated, you can't directly use them as extensions.
Instead of manually converting all those methods into extensions (which can be time-consuming and error-prone),
you can leverage Manifold's built-in functionality to automate this process. By adding the utility class as a parameter to the
@Extension
annotation, you can easily incorporate its methods as extension methods.For example, to use methods from
java.nio.file.Files
as extension methods forjava.nio.file.Path
:With this approach, all
public
,static
methods from theFiles
class that take aPath
as their first parameterwill be automatically available as extension methods for
Path
objects.