Gjum / Gjum/Tradex

Namelayer group restriction

Open
#13 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
5
Forks
4
PR merge metrics
No merged PRs in 30d

Description

An exchange may be restricted to players on a Namelayer group.

  • Read from chat and store in DB
  • Filter during search to exclude group-locked exchanges by default
  • Optionally allow all groups (or only some) during search

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Trace how exchange data is read from chat, stored in the database, and filtered during search. Define how Namelayer group restrictions are represented and how default versus unrestricted or group-specific searches should behave. Done means all three listed behaviors work together and group-locked exchanges are excluded by default.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, database, search
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.