coderabbitai[bot]
coderabbitai[bot]
## Background Currently, agenda folder validation logic is duplicated across different mutations. This includes checking if: - The folder exists - The folder belongs to the correct event - The...
The event topic in deleteChatMessage resolver uses ':chat_messages::create' for deletion operations, which is incorrect and could cause confusion for subscribers. ### Current Behavior The current implementation publishes deletion events with...
User @drazisil requested a review regarding removal of unused parameters. For more details, see PR #2350: https://github.com/rustymotors/server/pull/2350 And the specific comment: https://github.com/rustymotors/server/pull/2350#discussion_r1898974007 @drazisil
## Background This is a follow-up to issue #3319. The first part of the original issue has been completed - the pull request leaderboard now shows contributors who don't have...
## Tagging System Improvements This issue contains a checklist of proposed improvements to the tagging system to enhance organization and searchability. ### User Interface Enhancements: - [ ] Create a...
Track picking the custom pathToRegexpModule feature from #11 to master branch. Context: - Original PR: #11 - Feature: Support custom pathToRegexpModule This issue tracks the work needed to pick this...
# Universal Request Binding: ctx.Bind().All() ## Overview This proposal suggests adding a new `All()` binding method to the Fiber framework that would bind data from multiple request sources (query parameters,...
We propose implementing the fluent concept for the methods `Status` and `Type` in the Fiber framework using generics, as discussed in the following articles: - [Generic Interface Functions in Go](https://appliedgo.com/blog/generic-interface-functions)...
Based on the discussion in [Issue #3175](https://github.com/gofiber/fiber/issues/3175), we need to extend context support to other middlewares for consistency. Middlewares to update: - [ ] keyauth - [ ] csrf -...
The current implementation accepts non-RDF/XML formats with a warning, but the requirement states that ontologies **must** be in RDF/XML format. Consider implementing stricter format validation to ensure compliance with this...