❇️ Feature flagging framework in Swift sauce

Bug Report

| Q | A | | ------------------- | ------ | | BC Break | no | | Version | 1.3.1 |

Summary

I'm setting providers: [FeatureFlagLocalProvider(), FirebaseRemoteProvider()]. for this property

default: True localProvider: True firebase: False

Current behavior

The flag resolves as false, somehow deciding to choose firebase over the localProvider

How to reproduce

unsure, it seems like it should just work if you do [localProvider, firebaseProvider]

Expected behavior

the flag should resolve as True, respecting the local provider over the firebase provider

I generated a Xcode project from the Swift Package and imported the generated Xcode into my workspace.

I get the following error when compiling my workspace

My main use case is to be able to use this library together with tuist. The discussion about this use case is here

Feature Request

Allows reset of values inside a collection both via call and inside the browser of flags.
This feature should be also implemented to reset a single flag.
The scope is to reset any writable provider (ie. for LocalProvider it will remove the dictionary serialized file) and so on.

| Q | A |------------ | ------ | New Feature | yes | BC Break | no

Feature Request

Give the opportunity to alter the default value of a Flag.
Sometimes you may need to alter the default value specified inside the property wrapper signature. This happens if you want to define a single collection file used in several targets of your project where one or more flags have different default values.
In this case you can avoid to replicate the same collection blueprint but just change the default value.

A new call setDefaultValue() is therefore provided to allows this change.

| Q | A |------------ | ------ | New Feature | yes | BC Break | no

Feature Request

By calling flagValue(from:fallback) function from any FlagLoader concrete implementation value obtained ignores the fallback parameter which means "return the default value if nothing found on any provider".
Fallback is always returned when loader's reference is not available, while in case everything is setup correctly and no values were found the returned value is nil instead of defaultValue.

| Q | A |------------ | ------ | New Feature | no | BC Break | yes

Added the following features:

• #15 Give the opportunity to alter the default value of a Flag by using setDefaultValue() (example: loader.nested.$flagInt.setDefault(100, providers: [...]))
• #16 Reset values for LocalProvider and per flag in every writable provider (using resetValue() for Flag and resetAllData for LocalProvider.
• #15 Added more unit tests

Feature Request

While it's more complete, especially for debug purpose, the flags browser interface is far from being simple. Especially if you want to expose it to your non-tech managers the resulting experience is really poor.

We'll work on the following issues:

• [x] Simplify the initial flags collection list showing only the relevant informations (without describing the type of collection but exposing a metadata section event for FlagsCollection type).
• [x] Allowing in-place toggle for the most common used data type: the boolean. When you open a flags collection you should be able to change the value of boolean flags directly from list. This should works only if flag has one or more writable providers (the toggle operation will affects all the writable data providers like the LocalProvider).
• [x] Show relevant errors when set the value of a flag

| Q | A |------------ | ------ | New Feature | yes | BC Break | no

The following screenshots describe the expected result:

Bug Report

LocalProvider class fails to throw errors when saving internal flags dictionary inside a local file making the error catching really difficult.

| Q | A | | ------------------- | ------ | | BC Break | yes | | Version | 1.1.0 |

How to reproduce

Just allocate a new LocalProvider pointing to an URL of a directory instead of a file.

Expected behavior

public func setValue<Value>(_ value: Value?, forFlag key: FlagKeyPath) throws -> Bool where Value: FlagProtocol support throws but the saveToDisk() function does not throw, instead it uses optional throw via try?.

Just remove it to fix the issue.

Bug Report

FirebaseRemoteProvider's wrappedTypeFromOptionalType() function does not work correctly with non optional type and fails returning nil values even for available flags. This causes wrong behaviour by querying remote provider for set values.

Fix

Fix includes fallback value for wrappedTypeFromOptionalType which allows us to return the unwrapped value correctly:

public func wrappedTypeFromOptionalType(_ type: Any.Type) -> Any.Type? {
    (type as? OptionalProtocol.Type)?.wrappedType ?? type
}

Bug Report

Bundle is currently loaded by getting Bundle(for: Self.self) in extension of Bundle inside the package.
However Bundle's path is set to:

<AppName>.app/Frameworks/RealFlags.framework/RealFlags

but now the bundle is inside RealFlags.bundle.

How to reproduce

Using the package via CocoaPods and instantiate a new controller via the default create() of the controller.

Fix

Allows the bundle function to search inside the package itself if generated:

extension Bundle {
    
    private static let internalBundle = Bundle(for: FlagsBrowserController.self)
    
    internal static var libraryBundle: Bundle {
        #if SWIFT_PACKAGE
        Bundle.module
        #else
        [
            Bundle(url: internalBundle.bundleURL.appendingPathComponent("RealFlags.bundle")),
            internalBundle
        ].lazy.compactMap({ $0 }).first ?? Bundle.main
        #endif
    }
    
}

This PR add support for computed value for annotated @Flag properties.
This feature allows you to define a closure function which may return a custom value for an annotated flag.
If value returned from callback is not nil this is the value of the flag and no other checks are made.
If the value returned is nil the flow continues by asking to any provider specified (in order) and eventually returning the fallback return value.

This is an example:
Suppose you have a feature flag called hasPublishButton: it should return true only when the app's language is set to it. This is how we should define this behaviour:

public struct MiscFlags: FlagCollectionProtocol {

    // MARK: - Flags

    @Flag(default: false, computedValue: MiscFlags.computedPublishButton, description: "")
    var hasPublishButton: Bool
            
    // MARK: - Computed Properties Functions

    public init() { }

    private static func computedPublishButton() -> Bool? {
        Language.main.code == "it"
    }
}

What problem are you facing?

Ive added a fork to support firebase 10.0. This was needed to resolve captcha issues with the simulator and firebase auth captcha

https://github.com/tr736-reclip/RealFlags

Other Information

No response

@malcommac Thanks for the great package. My app is currently supporting iOS 11+

I see it's quite trivial to change the codebase a bit to support iOS 11. I don't see any reason why we shouldn't do that.

Hope I haven't overseen something here 😬

Feature Request

| Q | A |------------ | ------ | New Feature | yes | RFC | no | BC Break | no

Summary

First of all, thank you for the great library. It looks modern and easy to use.

I'd suggest to add a simple demo app into this library, so that other can easily start play around with the library immediately without initial setup.

Feature Request

At this time all the optional data is showed using Optional(Value) string inside the browser. This is just the debug description form coming from the Swift runtime. We should optimize it by showing the data if available eventually with a small icon to inform about the optional nature.

| Q | A |------------ | ------ | New Feature | yes

Feature Request

http://optimizely.com as Firebase Remote Config allows you to configure A/B test and feature flags. It should be a great new data provider to add.

| Q | A |------------ | ------ | New Feature | yes | RFC | no | BC Break | no