By default order tickets by last updated, if not otherwise defined.
---
 tests/test_search.py           | 115 ++++++++++++++++++++++-----------
 todosrht/blueprints/tracker.py |   3 +-
 todosrht/search.py             |  32 ++++++++-
 3 files changed, 109 insertions(+), 41 deletions(-)

diff --git a/tests/test_search.py b/tests/test_search.py
index 5f87887..624abf5 100644
--- a/tests/test_search.py
+++ b/tests/test_search.py
@@ -1,5 +1,6 @@
 import pytest
 
[message trimmed]

This adds ordering by id and updated, using ! for reversing, similar to
negation of terms. E.g. sort:updated, !sort:updated.

I wanted to add ordering by number of comments, but it required changing
the base query to include the comment count, which was a pain to get to
work correctly using sqlalchemy so leaving it for later.

Ivan Habunek (1):
  Implement ticket ordering

 tests/test_search.py           | 115 ++++++++++++++++++++++-----------
 todosrht/blueprints/tracker.py |   3 +-
 todosrht/search.py             |  32 ++++++++-
 3 files changed, 109 insertions(+), 41 deletions(-)

Thanks, applied. Sorry for the longish wait.

Ivan

Thanks, applied.

-- Ivan

On Fri, 28 Aug 2020, at 21:23, Denis Laxalde wrote:
> It might also be nice to support more than one parameter. E.g.
> "sort=-creation_date,title", meaning sort by creation_date reversed,
> then title.

It might be simpler to specify sort multiple times, e.g. 
`sort=-creation_date sort=title`, or whatever syntax is agreed upon.

I actually have a WIP patch for sorting, could finish it up.

Ivan

On Sun, May 24, 2020 at 07:26:18AM +0000, Simon Ser wrote:
> IMHO rendering as checkboxes is already a step forward. I don't mind
> having to edit the Markdown source to update the checkbox status.

I agree with Simon. Having read-only checkboxes is better than not
having them at all.

-- Ivan

On Sun, May 24, 2020 at 07:25:01AM +0000, Simon Ser wrote:
> There's a "readonly" attribute that makes it look like regular
> checkboxes while being immutable.

The readonly attribute does not apply to checkboxes unfortunately.

MDN says:
"Note: Only text controls can be made read-only, since for other
controls (such as checkboxes and buttons) there is no useful distinction
between being read-only and being disabled, so the readonly attribute
does not apply."

I would argue that visuals are a useful distinction, but hey.

On Sat, May 23, 2020 at 08:43:38AM -0400, Drew DeVault wrote:
> Yeah, it would only work for ticket descriptions. But that's not the
> hard part: the hard part is extending the markdown parser with
> line/colno annotations, so that we know what characterse to edit to
> apply the change.

Is that even possible in Misaka or would you have to change Hoedown?

Apparently FSX is working on replacing Hoedown:
https://github.com/FSX/misaka/issues/69

I can see why this issue is unresolved.

-- Ivan

On Sat, May 23, 2020 at 08:40:07AM -0400, Drew DeVault wrote:
> The problem with either approach is that the checklists are read-only.
> Making checklists has never been difficult; making them writable has
> been.

I didn't realize that was a wanted feature. It does complicate things,
e.g. editing comments is not permitted at all currently.

-- Ivan

---
 srht/markdown.py                   | 27 +++++++++++++++++++++++++--
 srht/static/icons/check-square.svg |  1 +
 srht/static/icons/square.svg       |  1 +
 3 files changed, 27 insertions(+), 2 deletions(-)
 create mode 100644 srht/static/icons/check-square.svg
 create mode 100644 srht/static/icons/square.svg

diff --git a/srht/markdown.py b/srht/markdown.py
index b48d2a4..9e2fc6b 100644
--- a/srht/markdown.py
+++ b/srht/markdown.py
@@ -10,7 +10,7 @@ import bleach
 import misaka as m
[message trimmed]