Closed ookami-kb closed 4 years ago
Awesome, @ookami-kb . Hero! I will definitely find sometime to review your PR this week so we can have a new version as soon as possible! ;)
@ookami-kb if you can update the example app in the repository, it would be a huge bonus for the community. It is always easier for people to adopt the new feature you have contributed if the example app has and example of its usage ;)
Even better if you also update the Readme in the example folder.
@ookami-kb awesome, thanls for the contribution, will be merging this and releasing a new version as soon as possible, probably in the next couple of days! :)
I plan to leave an explicit mention of your name in the version changelog, let me know if you are not comfortable with that.
Cool, nice to hear that!
Yeah, I'm totally ok with it 👍
Requirements
Related issues
Fixes #19
Describe the solution you've provided
Added optional
custom
argument toinit
method.Describe alternatives you've considered
No.
Additional context
No.
How to test?
Pass
Map<String, dynamic> custom
argument toinit
method (e.g.{'custom': 'value'}
). Check that the corresponding user in LD has this custom attribute set.Future works
custom
methods; if values are of the wrong type it ignores the value at all. For iOS, it just passes the argument as[String: Any]?
to user data.