Looks like a straightforward move
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Jun 2 2023
Looks good overall, might be worth trying box-shadow instead of blur if it's easy... but feel free to land as-is if it takes too long to investigate + achieve the same effect
change name from blur to glow
Maybe glow instead of blur? Kind of associate blur with being some sort of "filter" "above" some other content
fix text vertical alignment
Saw a css class that could be moved to a different file to improve readability
addressed feedback
rebase before addressing feedback
rebase and land
In D8056#239068, @ashoat wrote:In D8056#239034, @atul wrote:I can try to pull something generic out of CommunityCreationMembers and see if it can be used in other components where we have TagInput and UserList (ComposeSubchannel, AddUsersModal, etc) later in this stack.
That would be great
This diff makes sense, but from a code search it looks like it might impact ThreadSettingsLeaveThread and its use of otherUsersButNoOtherAdmins.
Since this is just a migration code path, I'm okay with it.
Looks fine to me, let bartek have a look
rust looks fine. Not a big fan of parsing text for certain values though.
Removed code duplication (function was introduced in D8010)
Comment and readonly
Extracted the shared code (here and not in D8013, because that's how I have my git stack set up).
Change the function to take a object of params, fix
Makes sense to me if the messages all get replaced & a local test of this seemed to work as expected
Rename 'parent admin' to 'Admins'
Rename "Parent admin" to "Admins" [discussed in DES-44]
Add comment
Jun 1 2023
In D8056#239034, @atul wrote:I can try to pull something generic out of CommunityCreationMembers and see if it can be used in other components where we have TagInput and UserList (ComposeSubchannel, AddUsersModal, etc) later in this stack.
Do we really need another low-level component for this? Don't we have something we can reuse? If not, can't we refactor something / make it generic, rather than implementing a new one of these?
Back to you with questions:
but I'm not clear on how all of them connect to the JS.