openwisp / openwisp/openwisp-controller
[change] Avoid loading advanced editor for commands
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 773
- Forks
- 315
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 14
Description
The command UI is generated using the same widget we use for configurations, but the advanced editor is not needed here, so we should find a way to avoid loading it.
Contributor guide
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 tracing how the command UI is generated from the shared configuration widget, then identify where the advanced editor is loaded. Done means commands no longer load the advanced editor while configuration views continue to use it; verify both command and configuration UI behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100