-
Viktor De Pasquale authored
The mechanism was replaced by loading updated directly by id to the initial list. There are two factors why yesterday-me was dumb: 1) By asynchronously loading update state, you have no control over it - hence no search 2) It's incredibly wasteful; running that hardcore search on every query? Not cool ...and from UX stand-point having updates inlined right under installed modules is by far better than nitpicking it from the list or in the search
332c1a6c
| Name |
Last commit
|
Last update |
|---|---|---|
| app | ||
| docs | ||
| gradle/wrapper | ||
| native | ||
| scripts | ||
| shared | ||
| signing | ||
| snet | ||
| stub | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| LICENSE | ||
| README.MD | ||
| build.gradle | ||
| build.py | ||
| config.prop.sample | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| settings.gradle |