Lantern-chat / Lantern-chat/server
Enforce text limits
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/Lantern-chat/server/commit/540fa174f8f0bb41a8fa90bc1b8eb121e253db49 removed in-database text limits, since PostgreSQL doesn't distinguish their representation anyway and we want them to be configurable.
Therefore, limits must be handled in application logic using a configuration object.
- Usernames
- Custom Status
- Biography
- Party Name
- Nickname
- Profile fields
- Room Names
- Room Topics
- Emote names
- Emote alts
- Role names
- Friend notes
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the application configuration object and the existing handling for Party Name and Room Names, then assess the remaining unchecked fields. Done means configurable application-level limits are enforced for each listed field.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, rust
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100