-
Notifications
You must be signed in to change notification settings - Fork 0
Create specification for technologies #12
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
Conversation
EliuX
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
KUDOS!
| title='Type', | ||
| max_length=30, | ||
| description='Id of user who first added this technology', | ||
| ), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, let's move these kinds of fields that are generated after creation, i.e. created_at, created_by, tenant_id, etc., to a model called technology_response, this way you will not require them when the technology is being created but this has to be autogenerated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those would be those ReadOnly fields
| @ns.route('') | ||
| class Technologies(Resource): | ||
| @ns.doc('list_technologies') | ||
| @ns.marshal_list_with(technology, code=200) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then in the @ns.marshal_list_with you will use technology_response.
…om/ioet/time-tracker-api into feature/create-technologies-spec#7
No description provided.