lokenx / lokenx/plexrequests-meteor
[Suggestion] Globally customizable $servername
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 521
- Forks
- 129
- PR merge metrics
- No merged PRs in 30d
Description
most people who you share your server with don't know what "plex" is. not my users anyway, they know it as what i named my server.
my suggestion is a $servername field in settings that will replace "plex" universally on the application with "$servername" ,making it less confusing for users, and more immersive in the plex environment as a whole.
god, i made that sound like a sales pitch.. lol.. anyway that's my suggestion
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
The issue names no files or tests. Start by locating the application settings entry point and the user-facing occurrences of “plex”; determine which occurrences should use a configurable server name. Done means the saved name consistently replaces the intended user-facing label throughout the application.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100