Looking for ideas!

[guillermomuntaner]

Hello everyone!

In order to extend the collection I am looking for new fresh ideas.

Thanks.

[own2pwn]

What about to create a poll to vote for the features to impement first?

[own2pwn]

I'd go for @Dependency

[yvbeek]

A few ideas:

• @BundleInfo: reads a key from Bundle.main.infoDictionary
• @Keychain: reads and stores values in the Keychain
• @NotificationHandler: subscribes to a specific notification and is automatically deallocated
• @Random: feed it an array and the get accessor returns a random element
• @CopyOnWrite: wrapper for isKnownUniquelyReferenced (see this post)
• @Debug: optional that is only initialized in debug mode (#if DEBUG)
• @Release: optional that is only initialized in release mode (#if RELEASE)

The names probably need a bit of tweaking 😄

[own2pwn]

@ZyphraX maybe @Secret(debug: "", release: "") ?

[andreamazz]

On top of my mind:

• @SafeArray: the subscript method returns an optional element, nil if the index is out of bounds

[yvbeek]

@ZyphraX maybe @Secret(debug: "", release: "") ?

Yes that could work, it reminds me a bit of Ruby Rails environment secrets.

Is it possible to make it generic? Can you for example do:
@Secret(debug: 10, release: 100) ?

[guillermomuntaner]

@ZyphraX maybe @Secret(debug: "", release: "") ?

Yes that could work, it reminds me a bit of Ruby Rails environment secrets.

Is it possible to make it generic? Can you for example do:
@Secret(debug: 10, release: 100) ?

Absolutely possible to use generics!

I am not sure those "secret" values should be in the souce code. It is a good pattern to keep them in config files/build settings which depend on the build configuration and read via bundle info.

[yhkaplan]

I would like to do a PR for something like @Compressed(maxSizeInMB: 10) that makes sure UIImage and Data properties are compressed to below a certain maximum limit. What do you think?

[Dimillian]

@Cached(name: String)
I'm not even sure PropertyWrapper are the right tool for that, but the idea is to provide a cache key to any optional property that you set later into your code (maybe on the .onAppear, or maybe once you receive data from an async call). The next time you use the same key, it'll fetch the value from the backing storage of @cached (a shared singleton which hold a map of [Key: Value]) and return it if available. And when you set the wrapped value it save it to the cache. Would be quite handy IMO in some case.

[guillermomuntaner]

@Cached(name: String) ...

@Dimillian a Cached property wrapper is on the todo list. I am still not sure about the cache implementation itself; either NSCache, a popular 3rd party or an easy way of plug in the cache itself.

[Dimillian]

Right I didn't saw thanks!

[mrigankgupta]

@obfuscate: encrypt and decrypt the string