You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 22, 2020. It is now read-only.
There's a lot of boilerplate in the search_form templates. A DSL to "automatically" add that boilerplate (form-group, form-notes, etc. etc.) to distinguish the interesting content from the boilerplate would be really neat.
YAML might be a good place to start, so a template looks like:
fields:
- title: Full text
input: <input name="search" id="search" class="form-control" placeholder="Your query..." value="{{= search.query_string.replace(/\"/g, """) }}" type="text">
notes: my notes whatever they are
Or:
fields:
- title: Full text
input: text/query_string
notes: my notes whatever they are
- title: Subject
input: text/subject
notes: my notes whatever they are
- title: Date sent
input: daterange/sent
notes: my notes whatever they are
(This idea isn't fully developed, but has a lot of freedom for how to implement it.)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There's a lot of boilerplate in the search_form templates. A DSL to "automatically" add that boilerplate (
form-group
,form-notes
, etc. etc.) to distinguish the interesting content from the boilerplate would be really neat.YAML might be a good place to start, so a template looks like:
Or:
(This idea isn't fully developed, but has a lot of freedom for how to implement it.)
The text was updated successfully, but these errors were encountered: