Had to factor the user-list-determining logic in listData so that I could pass it through ensNames.
Note that fixing the searching behavior to match on searches for ENS names will be handled separately.
Depends on D6435
Details
Details
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
| native/profile/relationship-list.react.js | ||
|---|---|---|
| 405 ↗ | (On Diff #21522) | The inputs into currentTags come from usersWithoutENSNames, so there is already one pass with useENSNames happening. This second pass is necessary in case somebody adds an entry to the TagInput before its ENS name is fetched |
Comment Actions
(Two of the files in the Test Plan aren't being shown because of the permissions thing)