I've started on this!

So I had a question about this. I want to finish this up but having issues with some of the UI pieces (PickTransportNetworkActivity, AboutActivity, AboutFragment, ContributorFragment) that rely on external dependencies for some ui binding. The ui classes in question use some of the mikepenz dependencies:

implementation 'com.mikepenz:aboutlibraries:6.2.0'
implementation "com.mikepenz:fastadapter:$fastadapterVersion"
implementation "com.mikepenz:fastadapter-commons:$fastadapterVersion"
implementation "com.mikepenz:fastadapter-extensions-expandable:5.3.4@aar"

I want to update their versions to the latest because they have been updated to support viewbinding, but I'm a little confused how to do that given the fact the project uses the gradle witness plugin. Would I need to manually update the witness file after updating the dependencies so that the checksum on each updated dependency matches what I see on the versions I update to?

Run this script after bumping the dependencies: https://github.com/grote/Transportr/blob/master/update-dependency-pinning.sh

Be aware that Mike Penz' libraries tend to introduce API breaking changes with new versions. So be sure to test thoroughly all parts of the app using these libraries...

@grote Great thanks i'll do that.

@ialokim So then should I add automated tests for related pieces as a part of that?

Also, where are all the variables defined that are used as placeholders for dependency versions?

Also, where are all the variables defined that are used as placeholders for dependency versions?

Did you mean these?

yeah. sorry i haven't forgotten about this. i've been having issues with some of the mikepenz libraries and updating those to use viewbinding.

No problem. Would you want to continue working on it or could you push the changes you already did somewhere so someone else could take over?

I wanted to continue working on it. When did you want me to have it in by?

We have no deadline. I just wanted to make sure that the work that you had already done would not get lost.

I imagine that updating the mikepenz libraries is a big task. Not sure whether we could do the migration in parts, i.e., leaving the fastadapter library updates apart for now?

Sure! I'll start committing what I have so far to a branch in my forked repository and submit and a PR for all of it when I've gotten it done. Any pieces that require bigger changes due to libraries being updated I'll leave out. Will summarize in the PR notes what I've left out!