recoded-org / capstone-turkey-react-paying-it-forward Goto Github PK

Is your Feature Request Related to a Problem/a Blocker? Please Describe.
N/A

Describe How the Solution Should Behave
The router hierarchy is responsible for link the appropriate component to a specific path.

Screenshots of the Design/if Any

Is your Feature Request Related to a Problem/a Blocker? Please Describe.
N/A

Describe How the Solution Should Behave
The home page component should be in the pages directory and the project card should be created in the components directory. You can use some fake data to render the components.

Screenshots of the Design/if any
(Add it after you finalise the figma design)

Additional Context
N/A

Search functionality in the Navbar will possibly be problematic, we already have categories on the donated and requested items and we might think about implementing the search functionality on the donated items and requested items pages respectively.

The search input field will be removed from the Navbar.,

Is your Feature Request Related to a Problem? Please Describe.
N/A

Describe how the solution should behave
The modules should be inside the components directory and called inside the navbar because they will be accessible from there.

Screenshots of the design/if any

Additional context
Use formik to handle validation.

Is your Feature Request Related to a Problem/a Blocker? Please Describe.
N/A

Describe How the Solution Should Behave
The Team page should display all the members who work in the development of the site .

Screenshots of the Design/if Any

Is your Feature Request Related to a Problem? Please Describe.
N/A

Describe How the Solution Should Behave
The FAQ page should be in the pages directory.

Screenshots of the design/if any

Additional Context
N/A

• Implement Login & Sign using userStore.
• Refactor code to use Auth,

Is your feature request related to a problem? Please describe.
N/A

Describe how the solution should behave

https://payingitforward.re-coded.com/api/docs/#/Auth/post_auth_signup

Please check the SwaggerUI link above. Registering a user needs the input we get from the users via our Sign Up module. Then we must make a POST request to the API to register a new user. The response message from the API must be shown to users via a notification. After Signing Up, the user must be routed to the Sign in module to Sign in.

https://payingitforward.re-coded.com/api/docs/#/Auth/post_auth_signin

For signing in we need to use the sign in endpoint and make a post request, then we must keep the info of the user in a users slice.

The slice name should be user and we need to set and get those data where needed, such as the Navbar.

Screenshots of the design/if any
N/A

Additional context
N/A

Is your Feature Request Related to a Problem/a Blocker? Please Describe.
N/A

Describe How the Solution Should Behave
The footer component should be displayed on all pages of the website, the component will be in the components directory in the src directory and imported into the app.js. All the links in the footer should reflect real pages on the website.

Screenshots of the Design/if Any

Additional context
Formik for input validation.
react-router-dom is already imported to the repo.
All routes should be a constant variable stored in the src/routes.js file and exported from there for ease of use.

Is your Feature Request Related to a Problem? Please Describe.
N/A

Describe how the solution should behave
The contact us page should be in the pages directory and the input forms should be validated using formik. The email should be sent using the email library.

Screenshots of the design/if any

Additional context
Formik for data validation.

Is your feature request related to a problem? Please describe.

Donated Items Page is the page the hold and shows us all the available items.

Describe how the solution should behave:

Fetch all the items from the backend into a slice called items.

Showcase the whole items on the Items page.

Once the user clicks on an item, they should move to the detailed item view via the router (take the item id and use it in the router) -in a modal or as a separate page- which will showcase the details and the owner of that item.

We should be able to filter the items via the buttons.

The item must be disabled when the count and the borrowers are equal. (isAvailable flag must be turned to false and the item must not render on the donated items page)

Items Endpoint
Filter Endpoint
Specific Item Endpoint

Screenshots of the design/if any

Additional context
N/A

• Fix link in Navbar Component
• Fix ItemCard in Donated Container

install tailwind and pull request

Is your Feature Request Related to a Problem/a Blocker? Please Describe.
N/A

Describe How the Solution Should Behave

The navbar should be displayed at top of each page on the website. The routing functionality should be implemented as well. The user should see the correct navigation pages and be able to click and move between them without any issues. The component will be in the components directory in the src directory and imported into the app.js.

Screenshots of the Design/if Any

(Add it after you Finalise the Figma Design)

Additional Context
react-router-dom is already imported to the repo.
All routes should be a constant variable stored in the src/routes.js file and exported from there for ease of use.

Is your feature request related to a problem? Please describe.

Requested Items Page is the page the hold and shows us all the requested items.

Describe how the solution should behave:

Fetch all the requests from the backend into a slice called requests.

Showcase the whole requests on the Requested Items page.

Once the user clicks on a request, they should move to the detailed request view via the router (take the request id and use it in the router) -in a modal or as a separate page- which will showcase the details and the owner of that request.

We should be able to filter the requests via the buttons.

Requests Endpoint
Filter Endpoint
Specific Request Endpoint

Screenshots of the design/if any

Additional context
N/A