@bit_sparkle Cyclic dependency.
IMO best way to solve is:
Make a common 3rd singleton that both of these singleton depend on.
Like for example, auth service cyclic deps with API service.
Make a base http client.
Both deps now use this common singleton.
@SuprDeclarative I think that one of the worst parts about flutter is their API design in terms of Text fields, forms and related.
They have relied too much on material, Cupertino widgets that it makes it super difficult to customize them and it's behaviour.
@ThomasBurkhartB@shiweidu@definev2@nank1ro@rsty_rafe Kind of bad until we can properly use the debugger with hot reload included at least, because not even with a key I have been able to do it.
Didn't dig into it that much, you can still just run (not debug) to make hot reload work.
Still some long road to travel 🤞
@otpamjak Don't have time to build a portfolio but can show you some of my work. If you need someone who you can just delegate things, feel free to dm me
@schultek_dev@FlutterDev You rock bro, would love to help you out on some issues in Jaspr so DM if you need some hand contributing or mediating on the issues.
@maxifirtman No es por defender a wsp, pero sabes lo difícil que debe ser testear una app que tiene bd internas personales con mil quinientas migraciones y además testear la conexión con el celu para hacer el sync de los chats y que no crashee ni enlentezca.
Mark: 'martes salimos como sea'
@wesostler@jaredpalmer@github Maybe a better option would be to have a way to create another re sync to second branch, which would create another PR after this one is merged.
I think this way because maybe the reviewer can miss reading the target branches.
@jaredpalmer@github When creating and a format is specified, use IA to auto generate the PR description. Then users should edit it as desired. Maybe this can be too expensive? But def worth investing for those lazy written PR