Documentation#624
Conversation
mrrogercampbell
left a comment
There was a problem hiding this comment.
Please fix the comments below. I did not mark all of them
|
|
||
| Step One: When under 1000px, password requirements box stays the same size - but the input fields change size, are no longer lined up, and are not centered. The text input boxes need to remain the same size, or be centered upon screen resolution shrink. | ||
|
|
||
|  |
There was a problem hiding this comment.
It doesn't seem like this image is working properly. Take another look for me please.
|
|
||
| ## URL Route | ||
|
|
||
| "/community/view-group" |
There was a problem hiding this comment.
Please put this in a backtick quote, so it looks like this:
/community/view-group
|
|
||
| ## URL Route | ||
|
|
||
| "/forum-page" |
There was a problem hiding this comment.
Please put this in a backtick quote, so it looks like this:
/forum-page
|
|
||
| ## URL Route | ||
|
|
||
| "/forum-page-hashtag" |
There was a problem hiding this comment.
Please put this in a backtick quote, so it looks like this:
/forum-page-hashtag
|
|
||
| ## URL Route | ||
|
|
||
| "/forum-page-topic" |
There was a problem hiding this comment.
Please put this in a backtick quote, so it looks like this:
/forum-page-topic
| ``` | ||
| { | ||
| title: "yourtitle", | ||
| description: "a description" | ||
| } | ||
| ``` |
There was a problem hiding this comment.
Please add js to the beginning three back quotes, so it looks like this:
{
"title": "yourtitle",
"description": "a description"
}| ## Request Example | ||
|
|
||
| HTTP Methods: GET, UPDATE, DELETE | ||
| `` fetch(`${BASE_URL}/groups/<int:pk>`, { headers: { Authorization: `Token ${localStorage.getItem("token")}` } }) `` |
There was a problem hiding this comment.
Please fix this one also.
There was a problem hiding this comment.
fetch(`${BASE_URL}/groups/<int:pk>`, {
headers: {
Authorization: `Token ${localStorage.getItem("token")}`
}
}) | HTTP Methods: GET, UPDATE, DELETE | ||
| `` fetch(`${BASE_URL}/groups/<int:pk>`, { headers: { Authorization: `Token ${localStorage.getItem("token")}` } }) `` | ||
| if UPDATE request body should include an object with the name of the field, you want to update set to its new value ex. `{title: "King of England"}` | ||
|
|
| ## Request Example | ||
|
|
||
| HTTP Methods: POST, GET | ||
| `` fetch(`${BASE_URL}/media`, { headers: { Authorization: `Token ${localStorage.getItem("token")}` } }) `` |
| HTTP Methods: POST, GET | ||
| `` fetch(`${BASE_URL}/media`, { headers: { Authorization: `Token ${localStorage.getItem("token")}` } }) `` | ||
| If a post request, expects the following request body format | ||
| `{ time: Date, image: Image, title: "yourtitle", description: "a description", optionally, the request can include author: Foreign Key of accounts.Profile, hashtag: Foreign Key of community.Hashtag, group: Foreign Key of community.Group, }` |
mrrogercampbell
left a comment
There was a problem hiding this comment.
@skut21x-ga Please see the comment below.
| { | ||
| "author": Foreign Key of accounts.Profile, | ||
| "hashtag": Foreign Key of community.Hashtag, | ||
| "group": Foreign Key of community.Group | ||
| } |
There was a problem hiding this comment.
You need to either place Foreign Key of accounts.Profile, in quotes or provide a sample value that goes there and then have a legend below that explains what to pass in.
Example:
{
"author": "<Foreign Key of accounts.Profile>",
"hashtag": "<Foreign Key of community.Hashtag>",
"group": "<Foreign Key of community.Group>"
}or
Example:
{
"author": "1",
"hashtag": "3",
"group": "15"
}| Field Name | Value |
|---|---|
| author | Foreign Key of accounts.Profile |
| hashtag | Foreign Key of community.Hashtag |
| group | Foreign Key of community.Group |
|
|
||
| - Deployed on Netlify: https://cotripper.netlify.com/ | ||
|
|
||
| #### Seeding Heroku |
Related Issue (include '#'): Not associated with an issue number.
Description of changes made: Added detailed documentation to README.md reflect the front-end and back-end contributions of SEI36, and provided recommended next steps for future contributors.
@clarknoah @rc1336