emplea-do / admin.emplea.do Goto Github PK

Write a service that...

CAN

GET

A list

• Employers jobs
• Jobs filter by their status (approved or dismissed)
• Jobs filter by the employer (❓)
• Jobs filter by date (❓)

POST

A new

• Job employer request
• Job employee proposal (❓)
• Sign up user
• Sign in session

A change (PUT, PATCH)

• Job employer request

@amaurygomez @claudiosanchez
If anything's missing, please let me know.

Cheers! 🥳

The employer page has a list of all created offers and an option to create a new one. In the list, the Employer must see the vacancy status, the number of applicants one by one and, if you click there, see all the people who have applied and their information.

The employer or Administrator send automatic emails with a default template with the vacancy to any group or any channels?

Implement design Ideas about the Job listing page with two columns pattern:

Right side: Jobs items with minimum information
Left side: Jobs Details with Action buttons

Self descriptive title

• Adds Jenkins integrations for running tests

Creates a Google OAuth Reac Admin Provider for sign in and sing out into the admin board.

Here's more oficial docs on how to implement Google Auth in our apps.
https://developers.google.com/identity/protocols/OAuth2

Add filter options to jobs datagrid.

As a admin user, I would like to see all the details of a job application once I click a item on Job List section

AC:

• It displays a Show component of jobs containing all information related of the job.
• It has two actions button (approve/deny)

On the SCSS it has to be configured the following elements for the UI:

• Typography
• Colors
• Margin/Paddings
• etc.

Implement React Suspense which uses React's error boundaries to catch the thrown promise, and sets a loading state for us, rendering the fallback component (Loading).

Self descriptive title.

Create route structure with history and react router dom.
Also private route with an auth service for validate token of the API, the api will use JWT token. The token will have role, lifetime and username or profile informations

Create a login page like the actual site of empleaDO with different providers.
The API will validate if the user have a role like Administrator or employer.

I suggest changing the repo name of employee.do by admin.emplea.do or something related to it, I get confused with the main project name employed_do

Create a view for the current user profile, with all the informations important about him and change password or others things we add in the future

Create a HTTP provider for making request to empleado.site

Create a list where you can see all published publications organized by most recent ones to be accepted or rejected, a tab for rejected and another for accepted publications, on the right side of the list a preview card of the publication data.