cronekorkn/left4me
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(blueprint): strip create-modal to name-only

Browse source 
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:
mwiegand 2026-05-17 00:03:57 +02:00
parent bee0f07d2f
commit 338b7baff3
No known key found for this signature in database
1 changed files with 5 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
l4d2web/l4d2web/templates/blueprints.html
View file

@ -33,9 +33,11 @@
</div>
<div class="modal-body">
<input type="hidden" name="csrf_token" value="{{ session.get('csrf_token', '') }}">
<label>Name <input name="name" required></label>
<label>Arguments <textarea name="arguments" rows="8" spellcheck="false"></textarea></label>
<label>Config <textarea name="config" rows="8" spellcheck="false"></textarea></label>
<label>Name <input name="name" required autofocus></label>
{# Arguments, config, and overlay assignments are edited on the
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 class="modal-footer">
<button type="button" class="button-secondary" data-modal-close>Cancel</button>