If you try to sign in without an email on the login screen, it crashes!

Hackers need to be assigned QR codes for food and activity tracking throughout the event.

To be used to give users a response for an action, kind of like this:
http://bootstrap-notify.remabledesigns.com/

We need styling on NumberFormat.tsx component. This component is for anything that relates to number input, such as: date, year, phone number, etc.

This file can be found here: https://github.com/hackmcgill/hackerapi-frontend/blob/develop/src/shared/NumberFormat.tsx

Redux is the most popular way to manage state alongside React. Its main advantage is avoiding the hassle of passing app-wide state locally via props from component to component, which allows it to scale much better than a solely local state solution.

Setup should just involve installing packages and setting a few folders up.

Mainly because bus checkbox has: BUS_REQUEST_SUBTITLE.

Want to make sure that if someone navigates to reset password, they must have the token to do so.

• Update copy of application questions to be consistent
• Fix typos
• Change Droplr to Dribbble
• Update sign-in page copy

After a user has created an account, they will receive an email to fill in the details with respect to the type of user they are (hacker, sponsor, volunteer, admin, etc.). They can access the component only if they provide a token generated by the API that gives them access.

If someone enters in email / password & clicks register, they should have their info carried over to the other page.

• Textarea.tsx
• Autosuggest.tsx
• Checkbox.tsx
• NumberFormat.tsx
• File upload

Implement 404 page
Add to react-router

Links from Reset password Component #9

Currently, we use a lot of custom components to accomplish many things. This means that our imports on top of files get very cluttered.

I'm proposing that for the shared, components, and containers folders, we have an index.js file that exports all the components so that we can have cleaner imports when we use stuff.

Example:

import { H1, H2, Paragraph } from `src/shared/`;

Currently a lot of lag when list renders.

TypeError: Cannot read property 'email' of null

LoginContainer.push../src/containers/login.tsx.LoginContainer.handleSubmit
src/containers/login.tsx:116

  113 |  * Function that calls the login function once the form is submitted.
  114 |  */
  115 | private handleSubmit(): void {
> 116 |     UserInfoController.logIn(
      | ^  117 |         this.state.email,
  118 |         this.state.password
  119 |     ).then((value: AxiosResponse) => {

Currently, our error states only involve console.error calls and red borders for inputs. We should have a better system to give clear input to users about why they aren't able to submit stuff (e.g. network issues, invalid email or password, etc.)

This would require some work from @hackmcgill/design to mock up what more complex would look like throughout the registration form.

Currently, we only have this guideline, and only for text inputs:

cc @pierreTklein

To access page, use the following link:
http://localhost:1337/password/reset?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJyZXNldElkIjoiNWMwNmNjOWFlNjI0YzY3YmYwNmRkNmY3IiwiYWNjb3VudElkIjoiNWMwNGRjYmY0NzhkYWM1MTVhNTdlZTU4IiwiaWF0IjoxNTQzOTUwMTY2LCJleHAiOjE1NDQwMzY1NjZ9.GpBWulL_IkNX64wnQNm8a_PIF9bnAWsi-Uy_6LqVuYA

👋

I'd like to maybe start a discussion on how we can reorganize our folder structure and file names so that our directories feel less bloated.

As a refresher for what we currently do:

• Individual components belong in src/components.
• Page containers belong in src/containers.
• All styled components belong in src/shared. Styled third-party components have the prefix Styled_____ in their file names.
• All HOCs belong in src/hocs.
• API wrappers belong in src/api.
• Constants belong in src/config.

A few things I've noticed:

• We probably need a new folder for utility .ts files.
• We have prop inconsistencies between all of the input components.
• Our file names are inconsistent.
• shared is more like styled?
• Might need to make subfolders for components
• We need to reduce the number of imports in every file (see #78)
• src/config is also hosting a bunch of abstractions as well.

Anyways, I'd like to maybe discuss what we could refactor as a Priority 2.

cc @hackmcgill/dev @hackmcgill/directors

As an admin or a sponsor, I want to be able to export information generated from my queries in order to manipulate it offline.

Right after logging in, I get the following error in my console:

Warning: Can't call setState (or forceUpdate) on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in the componentWillUnmount method.
    in ToastContainer (created by class_1)
    in div (created by Context.Consumer)
    in StyledComponent (created by Box)
    in class_1 (created by class_1)
    in class_1 (created by class_1)
    in class_1 (created by Route)

Only for when email is not confirmed.

Once you exit the confirm email page, it won't let users resend confirmation email again.

Classified as a bug since there is currently a way to make cache invalid.

Currently does not work