Closed gnunicorn closed 2 months ago
We are going to fork flutter tagger into our repo and start working from there replacing the existing mentions with our own implementation.
so, experimented with TypeAhead as an alternative, also pretty nice. However we face a similar issue here: We have to load the entire list of userIDs and displayNames once and check for them, thus potentially being a lot slower in even displaying the first set of items. If we were to use a riverpod-ish system though, we could have first checks go to ref.watch(memberDisplayName(..)).valueOrNull
and whenever the becomes available re-evaluate it. that'd actually be nicer.
also as a reference point, this has some nice usage pattern: https://pub.dev/packages/multi_trigger_autocomplete
but purely technically speaking, what do we need/care about at this point?
The list in 2 should probably just be a simple widget that we can then feed a riverpod consumer into so we can live update and don't have to wait for avatar data and stuff.
nice to have, follow up after:
#
to search rooms)
We have several issue that seem to directly come from our usage of flutter_mentions. The dependency is clearly not maintained at this point and we need to decide what we want to do about it.
Most notably it seems to cause: