Skip to content
This repository has been archived by the owner on Jul 6, 2019. It is now read-only.

feat(): implement file upload #4

Open
mianuddin opened this issue Aug 6, 2018 · 3 comments
Open

feat(): implement file upload #4

mianuddin opened this issue Aug 6, 2018 · 3 comments
Assignees
@stanleyarmstrong

Comments

@mianuddin
Copy link
Member

No description provided.

stanleyarmstrong added a commit to stanleyarmstrong/attendee-application-back-end that referenced this issue Aug 14, 2018
@stanleyarmstrong
feat(./application): add file upload
42823e7 
slohacks#4
@stanleyarmstrong stanleyarmstrong mentioned this issue Aug 15, 2018
Merged
mianuddin pushed a commit that referenced this issue Aug 16, 2018
@stanleyarmstrong @mianuddin
feat(application, attendee_application): add GET and POST for applica…
2346dcc 
…tion and user models (#6)

* feat(attendee_application/application, /attendee_application)

* feat(./application ./attendee_application): add User model

* fix(./application/views.py): fix typo in Users to User

* feat(./application): delete permissions on application

* feat(./application ./attendee_application): add application fields

#2

* feat(./application): add post view for user

#2

* fix(./attendee_application): add env variable for Secret Key

* fix(./application): fix application permissions atm

* chore(all): restructure directories (#7)

* chore(all): restructure directories

* chore(commitizen): update commitizen configuration

* refactor(./application): fix broken imports from cleaning up the project

* feat(./application): add file upload

#4

* style(./application): fix spacing in serializers

* fix(./application/serializers.py): fix post request on user model

* fix(./application/views.py): fix JSON requests

* style(./application/models.py): fix spacing in models
@mianuddin
Copy link
Member Author

Not actually completed by the last PR.

@mianuddin mianuddin reopened this Aug 16, 2018
@mianuddin
Copy link
Member Author

mianuddin commented Aug 16, 2018 •
edited
Loading

So, again, I don't think it's going to be possible to upload a binary file with JSON.

How about this?

  1. The file field is now a string, that takes in a hyperlink or maybe an ID.
  2. We create a new endpoint with a FileParser, so that the front-end can upload the resume. This route would either return a link or unique identifier (ID) that the back-end may use to identify the resume in question.

@stonewallstan @ohnoitsjmo @Jumer-Caragay

@stanleyarmstrong
Copy link
Contributor

So we could create a model for the file and give it its own view and endpoint. Then we would reference it with a related_name so it would be connected to the application. We could also probably still use the parsers that we have in this approach. Since multipart accepts files as well.

stanleyarmstrong added a commit to stanleyarmstrong/attendee-application-back-end that referenced this issue Aug 18, 2018
@stanleyarmstrong
feat(all): migrate to PostgresSQL
e862f74 
slohacks#4
stanleyarmstrong added a commit to stanleyarmstrong/attendee-application-back-end that referenced this issue Aug 18, 2018
@stanleyarmstrong
feat(all): migrate to PostgresSQL
5fc9a7a 
slohacks#4
stanleyarmstrong added a commit to stanleyarmstrong/attendee-application-back-end that referenced this issue Aug 18, 2018
@stanleyarmstrong
feat(all): migrate to PostgresSQL
0899d49 
slohacks#4
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@stanleyarmstrong stanleyarmstrong

Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mianuddin @stanleyarmstrong