Skip to content

Conversation

@ArushKhare
Copy link

@ArushKhare ArushKhare commented Jan 24, 2026

Fixed issues related to high code complexity (branch went to depth 19). Also, fixed a minor safety issue in the request.js file, which would try to extract data that had not been safely cached yet.

The chatroom refactor file seems to migrate chats to a different database. My refactoring seems to be within the scope of this file and the scope of the request.js file. This is because requests can trigger chatroom refactoring.

The issue originally made it harder to identify bugs within the software. This is because there wasn't much modularity. I split the original function into 4 different functions. Each function performed a specific task, making it easier to read. The fixes I made make the code more modular and easier to follow. I considered alternatives such as shortening some lines of code, but it seemed like a poor approach, as reducing lines can make code harder to debug later on (if you are looking for a specific issue).

To trigger the refactored code, I clicked on the opened chats.

uix qltylog

julianlam and others added 30 commits November 24, 2025 12:20
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…, if note assertion is called via search; manual pull)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
barisusakli and others added 30 commits January 16, 2026 13:00
only match [[namespace:key]] allow underscores,dashes and dots in namespace key
add test
fixes chat teasers and probably every other place where display name is shown
@julianlam tried accepts module ran into issues when the route was requested via browser or via $.ajax with the default headers,
for example accepts(req).type(activitypub._constants.acceptableTypes) still returns true when /post/123 is loaded via browser or via $.ajax
show fail count and sent count separately
fix paths in topic thumbs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants