Type of feature

✨ Feature

Current behavior

• no protected routes

Suggested solution

routes to be protected from unregistered site visitors:

• { path: "account-type", component: AccountTypeComponent }

•  {
   	path: "client", // TO-DO auth gard
   	component: DashboardComponent,
   	children: [
   		{ path: "projects", component: ClientProjectsComponent},
   		{ path: "", redirectTo: "projects", pathMatch: "full"},
   		{ path: "new", component: ClientNewProjectComponent },
   		{ path: "matches", component: ClientMatchesComponent },
   	],
   },
   {
   	path: "talent", // TO-DO auth gard
   	component: DashboardComponent,
   	children: [
   		{ path: "projects", component: TalentProjectsComponent},
   		{ path: "", redirectTo: "projects", pathMatch: "full"},
   		{ path: "new", component: TalentNewProjectComponent },
   		{ path: "matches", component: TalentMatchesComponent },
   	],
   },
  

### Additional context

_No response_

### I would be willing to submit a PR to fix this issue

- [X] Yes and I have read the [Contribution Guide](https://anguhashblog.com/contributing) and I agree to follow this project's [Code of Conduct](https://anguhashblog.com/code-of-conduct)
- [ ] No

Type of feature

📦 Chore

Current behavior

Code quality is not being checked either when developing or commiting

Suggested solution

Introducing some toolings:

• husky,
• lint-staged,
• eslint
• prettier
• stylelint

Aligning rules in .editorconfig and .prettierrc

Additional context

No response

I would be willing to submit a PR to fix this issue

• Yes and I have read the Contribution Guide and I agree to follow this project's Code of Conduct
• No

Type of feature

✨ Feature

Current behavior

• right now upon sign in redirect goes to dashboard
• dashboard can be ither client or talent

Suggested solution

• before redirecting to the correct dashboard new users with no user role must be redirected to the account-type component where they chose a role
• users with a role must not see this component route
• unregistered users also must not see this route apply route guard
• upon making a selection value is to be stored in the database

Additional context

No response

I would be willing to submit a PR to fix this issue

• Yes and I have read the Contribution Guide and I agree to follow this project's Code of Conduct
• No

Describe the bug

the GitHub link in footer points to https://github.com/PaidlanceDev

Steps to reproduce

needs to be changed to https://github.com/Paidlance

Browsers

No response

Additional context (Is this in dev or production?)

No response

I would be willing to submit a PR to fix this issue

• Yes and I have read the Contribution Guide and I agree to follow this project's Code of Conduct
• No

Type of feature

✨ Feature

Current behavior

There is no profile component

Suggested solution

Users should be able to view and update their details

• the other standard things I do
• add router link from home page to profile page

Additional context

I have created this issue for myself

I would be willing to submit a PR to fix this issue

• Yes and I have read the Contribution Guide and I agree to follow this project's Code of Conduct
• No

Type of feature

✨ Feature

Current behavior

it has copyright for all rights reserved

Suggested solution

Should be updated to say that paidlancer is an open source project

• the text must be more appropriate
• if needed consult with AI tool to adjust the footer notice accordingly
• Open Source MIT license

Additional context

No response

I would be willing to submit a PR to fix this issue

• Yes and I have read the Contribution Guide and I agree to follow this project's Code of Conduct
• No

Type of feature

✨ Feature

Current behavior

There is no scroll to top button

Suggested solution

This feature is to be implemented sitewide so it must be in the app.component.ts
two options of implementing:

• could be done using import {ViewportScroller} from '@angular/common'; view example
• or using import { HostListener } from "@angular/core"; view example

Additional context

PRs that do not follow the instructions provided here will be closed

I would be willing to submit a PR to fix this issue

• Yes and I have read the Contribution Guide and I agree to follow this project's Code of Conduct
• No

Type of feature

✨ Feature

Current behavior

Now there is social signing for google and for GitHub

Suggested solution

• add social signing with GitLab
• core team work since involves supabase

Additional context

No response

I would be willing to submit a PR to fix this issue

• Yes and I have read the Contribution Guide and I agree to follow this project's Code of Conduct
• No