spring2022-csci152 / team6 Goto Github PK

Get the front end profile page all the data it needs to display from the mongo db via the backend.

• Make "enter" key trigger search, too.
• Enable general search so that a substring of a field will find the course. Need to edit mongoDB feature.

Should be as simple as the inclusion of a utility function.

• Install bootstrap.
• Resolve differences between home and login pages so CSS can be uniform.

Ensure the password strength, and email format are checked correctly.

See Wiki and google docs: https://docs.google.com/document/d/16NwWi-si6sGQNzTjGivDXNJNIhafJLTRzkB0KNAsdw0/edit?usp=sharing

Modify original implementation so only the front end is tested instead of the entire integration(?).

Me and Vi are trying to figure out how to connect the pages and route the button to a different page.

Profile needs to be formatted for visual appeal and use (NFR).

Implement in the edit course module.
Need backend route, should check authorization.

• Play with and explore features of Jest.
• Create a dummy test case

Make it so only valid majors can be chosen, instead of a user created string.

See wiki and google docs: https://docs.google.com/document/d/1EHwml5-Dm630EffLgQoLJYbgilHAymfA3yH85Bb4iDU/edit?usp=sharing

Jest https://jestjs.io/ will work with react, node, and express.

Front-end

• design
• CSS

Back-end

• Store on database
• Retrieve from database

Issues with centering the components

Routes

• Sign-up: success
• Sign-up: fail
• Log-in: success
• Log-in: fail
• [ ]

Front-end

Sign-Up

Implement these functions in JavaScript first. Then create test cases on them.

• Check Password Strength
• Function implemented
• Test Case
• Check Email format "[email protected]" = [a-0]'@'[a-0]'.'[com+net+biz+org+edu]
• Function implemented
• Test Case

• Store as lowercase in database on sign-up
• Change to lowercase on login check.

• Connect to database
• Set up token system. Database creates temporary identification for user that is associated with their account. Front end stores token and sends for every page change or operation.

Need to understand how MERN stack maps to PHP aspect of WAMP/LAMP stack so that a pdf can be uploaded to server, and parsed. Seems like Express and Node both have something to do with it.

• Make the navigation bar at the top of the page detached from the main pages beneath it. This will avoid the need to include it at the top of every other page's code.
• Make the link to the currently viewed page stand out: highlighted or different color.

We don't need two pages: one for before login and one for after. We can use one and have it do different stuff based on the status of the user.

Example:
const [ user, setUser ] = useState(null)

if(user){
show logged in page}
else{
show logged out page
}

Troubles with hiding the CSS when nothing has been searched.

A prototype that only implements a CSCI major's suggested 4-5 year plan.

Front end

• Verify render of search box
• Verify render of submit button
• Verify default search string is empty
• Verify search string updates when characters are entered into search box
• Verify backend is called on submission

Create calendar module.

• Upgrade to google calendar.
• Make interactive with tasks.

Make sure pages that shouldn't be accessible arent accessible. You shouldn't be able to navigate towards pages by typing in the url. You also shouldn't be able to type in something random.

If a change is made in the edit view mode without a save to the backend and database, and then the view is swapped back to the regular basic mode, the change is still present even though that's not the course's true state.

Something is wrong with the json web token verification of the profile route.