1. Edwin Flatto - Scrum Master
2. Lisa Zeeb - Repo Owner
3. Rob Tisdale - DBA

This program is designed to brigde skill gaps of individuals to allow for users to show and improve their skills in order to help those who dont have them. It is based on reciprocity to incentivise "paying it

Users are able to login with username and password (if they dont have an account, they can register ) and be brought to their respective dashboard. Once there a user can see all upcoming tasks they have agreed to, as well as past tasks, their general rating and other pertinent information to the user. Once they navigate to the sites home page, they can engage with other users and requests tasks to be done

1. User can request a task to be done based on the skill required. Once posted, those with the pertaining skill will be notified there is a job they may be interested in.

4. User can edit their profile information and picture.
5. An administrator has access to a specific account which grants them overseeing privileges of all users. As well as activate and deactivate users.

TESTING CREDENTIALS User Username: Password:

Admin Username: Password: TESTING CREDENTIALS

Entities: and mapping

Repos, Service/Impl, Controllers

There are a lot of intertwining REST end point. The following are the most prominent of the project

Particular code notes:

SOMETHING FOR A PARTICULAR BIT OF TRICKY CODE TO LOOK OUT FOR

//controller

public void pasteNewCodeHere() {

}

Front end was broken up into several sub-directories:

1. Eclipse
2. Java / JPA /
3. git / github
4. Spring Boot
5. Gradle
6. MySQL / MySQl Workbench
7. Angular
8. TypeScript
9. Java Script
10. CSS
11. HTML

1. Mapping a composite key in Hibernate requires creating a separate class for the key and The @EmbeddedId annotation can be used to map the composite key in the entity class.

2. Learned how to work with a many-to-many relationship between four tables, where three of the tables are connected through a join table that has a composite key. This required understanding the use of the @ManyToMany annotation in Spring, along with the @JoinTable annotation to define the join table and its columns. It also required creating separate entities for the join table and the primary tables involved in the relationship, along with the appropriate mappings and methods to access the data.

3. When working with a four-way join table, it's important to specify all necessary join columns in the query with an And in the Jpa Repository query to find all necessary properties.

1. to use dynamic checkboxes in angular, generate from database using *ngFor. Two-way binding can be accomplished by creating a class called clickable, binding each checkbox property to that class (checked?:boolean) and then grabbing the objects from a list by name. This could probably be done better using an interface.

2. Reactive forms allow for modifying data before being added to a new object. For instance, it is easier to create dates because they can be formatted differently from plain HTML values. Also dynamically generating forms and getting input is more flexible.

3. Angular function calls are made on every update. So an *ngIF that has a function can get called 300+ times just on loading a component. Avoid by using property.

4. @Output, @Input for communication between parent/child components. More efficient than functions, which get called on every update.

1. When doing entity mapping,for something such as comment (which can have sub-comments), you can reference the actual entity with an "inReplyTo" attribute inside the entity.

    @OneToMany(mappedBy="inReplyTo")
	private List<Comment> comments;
	
	@ManyToOne
	@JoinColumn(name="in_reply_to_id")
	private Comment inReplyTo;
	

In this case I am using the existing table column