-
-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[API] Create Model for Projects Enpoint #80
Comments
As of PR #96, the field to reference tags should change to the following: tags = TaggableManager(through=TaggedItems, manager=CustomTaggableManager, blank=True) This field for guid should use UUID1: guid = models.UUIDField(default=uuid.uuid1, editable=False) and the imports at the top of the import uuid
from taggit.managers import TaggableManager
from django.conf import settings
from django.db import models
from django.utils import timezone
from django.contrib.auth import get_user_model
from tagging.managers import CustomTaggableManager
from tagging.models import CustomTag, TaggedItems |
Closing as no longer relevant to current development. |
Working on it now |
Fine to close! I thought the PR being merged would close the issue it was linked to directly 🤔 but note to self to double check (and make sure to loop back in the issue) 🎉 |
Based on the current proposed
projects
JSON, create aprojects
model for the corresponding DB tables to support theprojects
DRF app.JSON spec under discussion can be found in issue #77 , check there for any changes.
As of the writing of this issue, here is the JSON spec:
Base on that spec, here is a rough model, assuming that certain fields (user, date fields, tags, description, guid) would follow the
resources
model for their constraints and data types.The text was updated successfully, but these errors were encountered: