Workflow for Updates to generic_mapper
Open
Nobody has claimed this yet.
enhancement
question
- Dominant language
- Lua
- Stars
- 8
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Because we were unable to simply extend generic_mapper, the discMapper script will need to be manually updated when changes are made to the single file in the mudlet repo. How often do we do this? With every new Mudlet release?
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
Start by reviewing the linked generic_mapper.xml in the Mudlet repository and the discMapper script to understand what must be synchronized. Check how Mudlet releases affect that file, then document a clear update cadence and the conditions that require a manual discMapper update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100