BAndysc / BAndysc/WoWDatabaseEditor
[Feature] Client Area Trigger - Additional loop for showing existing scripts
- Dominant language
- C#
- Stars
- 564
- Forks
- 169
- PR merge metrics
- No merged PRs in 30d
Description
Would be nice and comfy if the picker could do a loop through Areatrigger_Scripts table to show if a script already exists in the picker.
AND/OR
A jump feature from Areatrigger_Scripts directly into the SmartScript editing
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the picker and its interaction with the Areatrigger_Scripts table, then inspect how the SmartScript editing view is opened. Clarify whether the goal is to show existing scripts, provide a direct jump, or both; done means the selected area trigger visibly exposes existing scripts and/or opens the corresponding SmartScript editor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- database, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100