rebase
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Thu, Oct 31
word boundry fix
use regex with word boundries
Created https://linear.app/comm/issue/ENG-9826/validate-the-ids-from-the-dm-operations to track the validation and assigned it to the cycle.
rebase and add destruction syntax for code clarity
use .includes instead of regex
Thinking about this. I think we should likely go with a non-regex solution as this is such a simple check. Going to change in next rebase
Makes sense to me!
In D13842#386643, @ashoat wrote:This diff introduces a new risk - an attacker can create a new thread with the same ID as an existing thin thread. Not sure how useful this attack could be. Protecting against it is handled in https://linear.app/comm/issue/ENG-9468/introduce-additional-validation-of-operations.
I'm a bit skeptical about introducing this regression. The task you linked is unlikely to be prioritized anytime soon.
This diff introduces a new risk - an attacker can create a new thread with the same ID as an existing thin thread. Not sure how useful this attack could be. Protecting against it is handled in https://linear.app/comm/issue/ENG-9468/introduce-additional-validation-of-operations.
In D13841#386565, @ashoat wrote:Do we really need a RegExp if we're just checking if the string contains another string?
Maybe the best argument for RegExp would be if we're trying to match on word boundaries.
Do we really need a RegExp if we're just checking if the string contains another string?
rebase
This approach sounds dangerous because it can potentially result in fetching a huge number of messages into memory. However, the scenario in which that could happen is almost impossible.
remove trimText code duplication with sidebar thread name function
address nit
Wed, Oct 30
rebase
feedback
rebase
review feedback
remove as
rebase
rebase
review feedback and changes
accidentally left a console.log
feedback and rebase
feedback and rebase