Extend taggable-mixin to support different Tag models.
Usage is pretty simple. Tag model is default in Taggable constructor but you
can call it with different model like GHOPTaskType that inherits from Tag model.
Both Taggable and Tag models have been updated and they don't use hardcoded Tag
model anymore and instead use cls of class methods or self.__class__. In case
of Taggable it's self.__tag_model.
indexes:
# used to list proposal in descending order of their score
- kind: StudentProposal
properties:
- name: org
- name: status
- name: score
direction: desc
# used to list reviews in ascending order of date
- kind: Review
properties:
- name: is_public
- name: scope
- name: created
# used to determine which orgs have more then 0 slots assigned.
- kind: Organization
properties:
- name: scope
- name: status
- name: slots
# used to order accepted orgs
- kind: Organization
properties:
- name: scope
- name: status
- name: name
# used to determine which proposals have a mentor assigned
- kind: StudentProposal
properties:
- name: org
- name: status
- name: mentor
# used to determine which proposals will be accepted
- kind: StudentProposal
properties:
- name: org
- name: status
- name: __key__
# used for the bulk mailing of students
- kind: Student
properties:
- name: scope
- name: __key__
# used for the cron system
- kind: Job
properties:
- name: priority_group
- name: status
- name: __key__
# AUTOGENERATED
# This index.yaml is automatically updated whenever the dev_appserver
# detects that a new type of query is run. If you want to manage the
# index.yaml file manually, remove the above marker line (the line
# saying "# AUTOGENERATED"). If you want to manage some indexes
# manually, move them above the marker line. The index.yaml file is
# automatically uploaded to the admin console when you next deploy
# your application using appcfg.py.