etiquette/frontends/etiquette_flask/etiquette_flask
Ethan Dalool 4c65ccaf68 Big! Liberate Groupables from strict heirarchy. Multiple parents.
I found that the strict heirarchy was not satisfying the situation
where one tag is the intersection of two others, but we can only
pick one as the parent

For example, does red_jacket belong under clothes.red_clothes or
clothes.jackets? A search for "red_clothes AND jackets" might
give us someone wearing red pants and a black jacket, so this
definitely needs to be a separate tag, but picking only one
parent for it is not sufficient. Now, a search for red_clothes
and a search for jackets will both find our red_jacket photo.

The change also applies to Albums because why not, and I'm sure
a similar case can be made.

Unfortunately this means tags no longer have one true qualname.
The concept of qualnames has not been completely phased out but
it's in progress.

This commit is very big because I was not sure for a long time
whether to go through with it, and so much stuff had to change
that I don't want to go back and figure out what could be grouped
together.
2018-07-20 13:09:06 -07:00
..
endpoints Big! Liberate Groupables from strict heirarchy. Multiple parents. 2018-07-20 13:09:06 -07:00
__init__.py Move ef/endpoints/common.py to ef/common.py 2018-02-03 01:43:41 -08:00
caching.py Switch to f-string formatting in many places. 2018-07-18 18:36:36 -07:00
common.py Big! Liberate Groupables from strict heirarchy. Multiple parents. 2018-07-20 13:09:06 -07:00
decorators.py Add decorator catch_etiquette_exception. 2018-01-09 21:21:15 -08:00
jinja_filters.py Big! Liberate Groupables from strict heirarchy. Multiple parents. 2018-07-20 13:09:06 -07:00
jsonify.py Further separate front & back; Create frontends folder 2017-05-01 21:49:28 -07:00
sessions.py Switch to f-string formatting in many places. 2018-07-18 18:36:36 -07:00