@variablepulserate Indeed…
Hectic day, it was almost scheduled to the minute. I’m more than happy that it is over now (only the regular evening stuff remains).
”Fixed” one issue that has been in the app since the 1.0 release. The word fix is in quotes because the root cause of the issue has been missing data from the backend, but instead of providing that data they introduced a new field that contains a part of the missing information. That means I added a special handling to the app to use that field to show the partial information we can interpret from it.
@matigo Hah. The project itself will have the documentation as part of the repository, the blog post is just an announcement to clarify what I have done and, hopefully, why I have done it.
Adding tests to the open-source project I am building is fun. More tests need to be added, though, before I make it public. Also, I have a couple of refactoring ideas that I might want to do before the publication, and I want to write a blog post about the project as well.
Okay. Got that one sorted out, the solution was to add a constraint to keep the content stick to the top of the safe area and then increasing the height to contain some safe area. Next up, adjusting the height of an options list based on the height of the individual elements (they can have 1 or 2 lines, depending on the app language and system text size).
// @matigo
Headache of the day: Adapting the height of a custom element on iOS based on the content height, especially when the system text size is increased. There were certain assumptions made back in the day, and those are no longer valid.
Forgot to start the exercise tracking, so I missed ~5 minutes from the start. In the end it does not matter, getting the exercise done is the main thing.
@matigo Yeah… Let’s see what the decision will be, that will then affect everything and we probably need to re-check every view of the app that has input fields (and as a banking app there are ”a few” of them…) to see if they got broken because of the font size change (especially on iOS, Android is much better when it comes adjusting the height of an element automatically).
Oh lovely. The customer's test manager reported a "bug" where the font size of the login input field is smaller than before on Android. I checked the code and, yes, the font size of all input fields has been reduced from 22pt to 18pt to match the app's design specification. Now, the test manager is pretty adamant that it should be changed back to what it was, so I asked our designers their input. Also, while debugging the issue I noticed that on iOS the font size is actually 24pt, thus being larger than what Android originally had and not matching the design specification, so we need to make changes to either 1 (iOS), 2 (pick 2 from Android, iOS, design), or even 3 (all) to make this one person happy.