Releases: saantiaguilera/feature-flags
Releases · saantiaguilera/feature-flags
v0.2.1
v0.2.0
- Add in
FeatureFlagResult
a boolean property denoting if it's enabled, hence removing the contract extension. This is in favor of java users, since kotlin ones already have sealed-class usage + reactive ones. Still, kotlin users can use the property, altough they are losing the contract for type inference (not a big deal since the existence of the above mentioned methods) - Add examples in all documentations. Accessible through docs
- Add in
FeatureFlagProvider
an inlined invoke companion operator, to create lambda providers without the hassle of a class definition - Remove in
FeatureFlagResult
both creational methods in favor of a single overloaded one at the companion (Java users also benefit from this)
v0.1.0
- Change open class to data class for
FeatureFlag
- Convenience method
isEnabled
for java consumers or if you don't care if the value was missing - Contract to
isEnabled
to return sealed inheritances when corresponding - Update dokka
v0.0.1
- Add
FeatureFlag
structure to generate Flag transfer objects. They
are based on golang flag pgk - Add
FeatureFlagProvider
contract that will decide if a given feature
is enabled / disabled. - Add missing concept, which will abide the default feature behavior. A
missing feature is still enabled or disabled, it simply wasn't found at
the provider and was a default value. - Add priority provider, which groups providers based on a comparator
priority - Add safe copy to providers in priority provider to avoid runtime
changes - Add creational methods to easily construct results
- Add functional scopes for reacting to an enabled / disabled / missing
result - Make functional scopes inline
- Use contracts API to ensure only one time it will be called a scope
- Add testapp with code samples
- Add dokka for javadoc
- Add publishing plugins to bintray and maven central
- Add SCA tools (detekt / ktlint)