You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 19, 2020. It is now read-only.
It is possible to register project extensions using types that won't necessarily be available on every project's build script compilation classpath.
This is the case for plugins injected via init scripts, for example.
Accessors for extensions with inaccessible types should carry documentation clearly stating so and have their types erased so they can be compiled successfully.
The text was updated successfully, but these errors were encountered:
- Move members to improve top-down file readability
- Replace lambda by constructor reference
- Replace `hasFlag` by `contains` operator for reduced noise
See #416
It is possible to register project extensions using types that won't necessarily be available on every project's build script compilation classpath.
This is the case for plugins injected via init scripts, for example.
Accessors for extensions with inaccessible types should carry documentation clearly stating so and have their types erased so they can be compiled successfully.
The text was updated successfully, but these errors were encountered: