-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thoughts on handling special licenses #29
Comments
Hello Kevin, and thanks for your feedback! I agree that this kind of licenses is problematic, but it seems like there’s no good universal solution. When I need to edit the licenses, I just update the |
Could you post some example here how to update the Thanks. |
@klwoon Sure. Here’s an example, I manually set the let viewController = AcknowListViewController()
viewController.acknowledgements = [Acknow(title: "Test 1", text: "ABC"), Acknow(title: "Test 2", text: "DEF")]
navigationController?.pushViewController(viewController, animated: true) An individual |
Thanks for the example! |
Howdy,
Thanks for this super useful tool! I just started using it and it's super helpful. One issue (not with your project) but when using GooglePlacePicker pod and a few other Google pods they actually have this weird license
I was wondering if you had any thoughts on how to best handle this? My thought is to subclass
AcknowListViewController
and overridefunc commonInit(acknowledgementsPlistPath: String?) {
then look specifically for these special license requirements.Would you be interested in having something that handles these special licenses by letting the
AcknowParser
take a list of overrides for ["pod name": some closure that returns a string]? Totally fine if you don't want to add that complexity.Cheers!
The text was updated successfully, but these errors were encountered: