feat(blueprint): strip create-modal to name-only
The new-blueprint modal had Name + Arguments + Config textareas, but the modal lives on blueprints.html (the list page), not on blueprint_detail.html, so neither textarea was wired to the srccfg editor — mixing themed-editor and raw-textarea UX in the same flow. Keep just Name; arguments/config are edited on the detail page where the editor lives. Add autofocus to the name field for keyboard flow. Server contract unchanged: create_blueprint (blueprint_routes.py:80) already defaults arguments/config to [] when absent from the form. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
bee0f07d2f
commit
338b7baff3
1 changed files with 5 additions and 3 deletions
|
|
@ -33,9 +33,11 @@
|
||||||
</div>
|
</div>
|
||||||
<div class="modal-body">
|
<div class="modal-body">
|
||||||
<input type="hidden" name="csrf_token" value="{{ session.get('csrf_token', '') }}">
|
<input type="hidden" name="csrf_token" value="{{ session.get('csrf_token', '') }}">
|
||||||
<label>Name <input name="name" required></label>
|
<label>Name <input name="name" required autofocus></label>
|
||||||
<label>Arguments <textarea name="arguments" rows="8" spellcheck="false"></textarea></label>
|
{# Arguments, config, and overlay assignments are edited on the
|
||||||
<label>Config <textarea name="config" rows="8" spellcheck="false"></textarea></label>
|
blueprint detail page where the srccfg editor + overlay picker
|
||||||
|
live. Keeping the create modal name-only avoids the conflict
|
||||||
|
where modal textareas can't host the editor cleanly. #}
|
||||||
</div>
|
</div>
|
||||||
<div class="modal-footer">
|
<div class="modal-footer">
|
||||||
<button type="button" class="button-secondary" data-modal-close>Cancel</button>
|
<button type="button" class="button-secondary" data-modal-close>Cancel</button>
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue