parambirje / jobsahoy Goto Github PK

Currently all the types in the project use

interface Example {}

We should replace all these interfaces to

type Example = {};

The JobsAhoy app being only the "public" side of the entire project, the database that this app needs is not being setup currently. The backend microservices are needed to dump data in the database so that it could be used by JobsAhoy.

We could proceed either ways:

• Could create a docker compose script to setup MySQL with some dummy data
• Create an example_data.sql file which has the schema, and dummy data (need to manually install MySQL)

Ultimately, automating all of steps needed in a package manager script command in the package.json that sets up the environment for us.

Dependent on:

• #5

When switching between the home route / (Landing Page) and the /jobs page using the Navbar, the layout shifts to the right and is not consistently placed across both the pages.

When a guest user (not logged in) goes on the /jobs route, the SignedOutPage.tsx view is incomplete/empty and needs to be designed accordingly with similar components used in the SignedInPage.tsx.

Additional Functionality:

• Should provide 5 job posting views (the guest user is allowed to view only 5 job postings and can view all after they sign-in)
• Can search using a job role using the search bar

The Log Out Button was removed earlier for UI redesigns.

It should now be implemented under /user/profile route using the signout function from next-auth.

As stated in the perf. improvement guide from vercel, react-icons is a bulky package that re-exports a lot of icons thus impacting the performance of the app.

All usages of react-icons should be replaced with phosphor-icons.

Refs #2
Mainly UI components in child routes inside /jobs that are needed to be refactored to close the issue.

• / #12
• /[jobId]

When "Dublin" is selected and applied as the Location filter, the page throws an error:

This is what's in console:

TypeError: Cannot read properties of undefined (reading 'length')
    at C (page-c20a3d13c80e2f36.js:1:22478)

The directory structure and components structure is not efficient nor scalable. The currect directory structure was made by keeping the 'pages' directory structure in mind, but is irrelevant as the 'app' directory revamps the organisation of the project files completely.

Need to organize files and components accordingly that are easy to manage and will scale efficiently to a bigger codebase.

Here are the official docs:
Getting Started: Project Structure
Project Organization and File Colocation

Routes going through UI component refactors:

• /components #15
• /user #4
• /jobs #11

Refs #2
Child routes inside /user that are needed to be refactored to close the issue.

• /create-account Fixed
• /login Fixed
• /onboarding #9
• /profile #10

The following components that are in /src/components:

• SocialLoginButtons.tsx
• /LandingPage
• GradientDivider.tsx (used by components in /LandingPage)

are not global components used by different routes, hence need to placed in respective local route directories.

For now the /user/logged-out page just outputs "Logged Out" in a div. Change this to a user-friendly logged out page with a suitable message and a call to action that directs them to the login page.

The compilation times for Nextjs v13 with server actions in beta have gone incredibly slow. Bumping up the version would seemingly improve the speed.

The route /user/create-account UI is ready but the backend functionality is not. In the current state users cannot create accounts using email and password. We can either completely remove this or put this in the next release.

The Landing page needs to be re-designed according to the features available at the moment.

Currently, most of the PropTypes are inline with the function definition

function MyComponent({ sample }:{ sample: string }){}

This should be avoided and be replaced with a type

function MyComponent({ sample }: MyComponentProps){}

type MyComponentProps = {
    sample: string;
};

The home page.tsx in the /jobs route switches views according to user's auth status. However the naming and hierarchy of these views and components are not consistent with the project navigation guidelines.

Inconsistent files:

• Components
• Views
• Helper functions
• Make a Global component for loading.tsx inside /jobs