Skip to content
This repository has been archived by the owner on Aug 19, 2020. It is now read-only.

Accessors for extensions with types not available to the build script #416

Closed
bamboo opened this issue Jul 10, 2017 · 0 comments
Closed

Comments

@bamboo
Copy link
Member

bamboo commented Jul 10, 2017

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.

@bamboo bamboo added this to the 0.11.0 milestone Jul 10, 2017
@bamboo bamboo modified the milestones: 0.10.2, 0.11.0 Jul 12, 2017
bamboo pushed a commit that referenced this issue Jul 12, 2017
For efficiency, and close them all at the end.

See #416
bamboo added a commit that referenced this issue Jul 12, 2017
 - Move members to improve top-down file readability
 - Replace lambda by constructor reference
 - Replace `hasFlag` by `contains` operator for reduced noise

See #416
bamboo added a commit that referenced this issue Jul 12, 2017
Add return type to factory functions so the correct type can be
inferred for `assertThat`.

See #416
bamboo added a commit that referenced this issue Jul 12, 2017
bamboo added a commit that referenced this issue Jul 12, 2017
 - Compute explanation on demand
 - Favour data class pattern matching over method dispatch

See #416
@bamboo bamboo closed this as completed Jul 12, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants