Guilherme C. Matuella

Added needs more info as there is still a lack of business logic definitions, such as: - Will we allow for it to be closed by dragging it down or...

Muito obrigado por abrir a issue @maxaraujo Iremos investigar mais a fundo o que está acontecendo para tentar solucionar o problema! Abaixo segue o crash log e possíveis issues relacionadas...

Muito obrigado por abrir a issue @enzodanjour! De fato o que o @mathmorais falou é o que acontece hoje. De qualquer maneira, acredito que isso seja um ponto de falta...

O PR https://github.com/olmps/memo/pull/161 deve ajudar em parte com este problema (o cursor não deve mais aparecer quando tocado na pergunta/resposta), mas ainda sabemos que é algo que acreditamos ter mais...

Added needs more info, as we still need to address the migration issue.

> then, with the admin SDK capabilities, every time an update occurs (in main branch) within this new folder of collections, run a script (using Github Actions, through a new...

> but I'm not sure if we are able to collect the file names that changed in a particular sub-folder. I've found a couple of alternatives if there is no...

Thanks for opening the issue @maxzorzetti! This is probably due to some Flutter limitations right now, like when the app initializes for the first time - imagine something like loading...

I think there could be workarounds for handling these shaders pre-warmup "manually", like calling these janky animations while still displaying a splash screen, although the effort necessary would be non-trivial....

This issue wasn't directly related to flutter jankiness, instead, it was due to a complex custom painter when painting a collection card. Attempted to solve it with other approaches (in...