-
-
Notifications
You must be signed in to change notification settings - Fork 386
Max Weight to Compose format #6309
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
base: master
Are you sure you want to change the base?
Conversation
Wow, you are relentless! 👍 Max weight... that has some similarities with the max height form - with the unit select, the input inside that sign graphic (for some countries) and all. Would you mind reviewing #6285 to make sure the implementation of both is consistent? (It's draft, not sure if he wants feedback so far, didn't yet ask) |
I will take a look and try to match more ! I must admit I already had somewhat of a skeleton here with a bit of a tree structure after looking at how they handled the one layer of signs the form asks for a GeneralMaxWeightSign and that returns depending on sign type |
And yeah, I must admit, I want Street complete on iOS, and the best way for that is to help! That and I love the idea behind the app so helping it even if it never gets on iOS is ALSO good! |
Well, TBH I only have had a cursory look at #6285, important basically is my feedback to @ltoenning about the structure so to not duplicate composable code for the different signs. I.e I don't know if he implemented it that way, yet: If all those sign layouts have both an input field and a unit selector dropdown (but depending on the sign it may be in- or outside of the sign layout), that means that there should be one composable for (length) input and one composable for the unit selector, separate from each other. The e.g. MaxWeightGeneralSign composable then glues those components together |
That makes sense yeah. I will spend some time looking at #6285 and try and make sure I go along with it! |
Working on Max Weight form