Event stats

[isa-leroux448]

Changes

• added bar charts, pie charts and stats tables to event stats page according to Figma
• created a percentage bar chart
• updated mock DB data type to match data currently stored in our registrations database
• edited stats table to work with same input data type as bar chart and pie chart

Out Of Scope

• backend connection

Notes

• I had some issues with the react google charts responsiveness where they wouldn't scale when I resized the screen. I added a function that reloads the charts on screen resize for both the pie chart and bar chart
• I don't think we store school value in our registration data so I omitted that chart
• Also had some styling issues related to conflicts between tailwind and inline styling using dynamic widths for the chart boxes so I ended up using a CSS module for simplicity

Image

Mobile.mov

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
biztech-v2	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 18, 2024 9:39pm

[isa-leroux448]

I ran into a slight type issue. I created a new type called "AttendeeDetailedInformation" based on the registration data in the DB. I edited the return value of the fetchRegistrationData function to use this type. However, I realize that we are using quite a few different types (e.g. type Attendee) to represent attendee data and I'm not sure if they should all use the same type? It's causing a type error in the check but I'm hesitant to change any types and mess up another part of the code.
Any recommendations? Should we consolidate the different types into one?

[AllanT102]

is total always gonna be non zero?

[AllanT102]

Types should be consistent with db. So i think this here should be "Registration"

[AllanT102]

I ran into a slight type issue. I created a new type called "AttendeeDetailedInformation" based on the registration data in the DB. I edited the return value of the fetchRegistrationData function to use this type. However, I realize that we are using quite a few different types (e.g. type Attendee) to represent attendee data and I'm not sure if they should all use the same type? It's causing a type error in the check but I'm hesitant to change any types and mess up another part of the code. Any recommendations? Should we consolidate the different types into one?

It's best to be consistent yes. I did a quick look and it should be fine using AttendeeDetailedInformation if that represents the registration information. currently fetchRegistrationData is used for the registration table on admin side and the stats page, so it won't be a large change.

Please change this field to be "Registration" so that it matches the db table name.

Also, the fetchBackend function is on dev now and it works. Please implement the call to the backend and fetch real data.

@isa-leroux448

[voctory]

I ran into a slight type issue. I created a new type called "AttendeeDetailedInformation" based on the registration data in the DB. I edited the return value of the fetchRegistrationData function to use this type. However, I realize that we are using quite a few different types (e.g. type Attendee) to represent attendee data and I'm not sure if they should all use the same type? It's causing a type error in the check but I'm hesitant to change any types and mess up another part of the code. Any recommendations? Should we consolidate the different types into one?

It's best to be consistent yes. I did a quick look and it should be fine using AttendeeDetailedInformation if that represents the registration information. currently fetchRegistrationData is used for the registration table on admin side and the stats page, so it won't be a large change.

Please change this field to be "Registration" so that it matches the db table name.

Also, the fetchBackend function is on dev now and it works. Please implement the call to the backend and fetch real data.

@isa-leroux448

Hey @AllanT102, do we need to get the backend functionality working in this PR? It might be better to merge our efforts to fetch event and registrations data on both the Stats page and the Admin Events Registrations page, otherwise we're duplicating the amount of work to get both pages working.

[AllanT102]

I ran into a slight type issue. I created a new type called "AttendeeDetailedInformation" based on the registration data in the DB. I edited the return value of the fetchRegistrationData function to use this type. However, I realize that we are using quite a few different types (e.g. type Attendee) to represent attendee data and I'm not sure if they should all use the same type? It's causing a type error in the check but I'm hesitant to change any types and mess up another part of the code. Any recommendations? Should we consolidate the different types into one?

It's best to be consistent yes. I did a quick look and it should be fine using AttendeeDetailedInformation if that represents the registration information. currently fetchRegistrationData is used for the registration table on admin side and the stats page, so it won't be a large change.
Please change this field to be "Registration" so that it matches the db table name.
Also, the fetchBackend function is on dev now and it works. Please implement the call to the backend and fetch real data.
@isa-leroux448

Hey @AllanT102, do we need to get the backend functionality working in this PR? It might be better to merge our efforts to fetch event and registrations data on both the Stats page and the Admin Events Registrations page, otherwise we're duplicating the amount of work to get both pages working.

True... ok let's do that @isa-leroux448 can you handle this then? Once you merge this in, I've assigned you the ticket to connect backend for registration table and stats

[voctory]

PR LGTM, will approve once the Vercel build passes

[isa-leroux448]

I fixed the userInfo component used in the attendee information popup to use the new Registration type and be able to handle the nested user profile information. Right now I'm running into issues when building with next but I don't think they're related to my branch. I think some broken stuff got merged into dev because the package.lock syntax is off and I get a whole bunch of errors like these when I run next build:
Error occurred prerendering page "/admin/home". Read more: https://nextjs.org/docs/messages/prerender-error
and
Error: NextRouter was not mounted. https://nextjs.org/docs/messages/next-router-not-mounted

[isa-leroux448]

Is this a problem with the other PRs? Wondering if it's something I should fix in my branch or another bug fix ticket altogether

[AllanT102]

I fixed the userInfo component used in the attendee information popup to use the new Registration type and be able to handle the nested user profile information. Right now I'm running into issues when building with next but I don't think they're related to my branch. I think some broken stuff got merged into dev because the package.lock syntax is off and I get a whole bunch of errors like these when I run next build:

please fix alongside this PR so it passes build, thanks

[voctory]

Any updates @isa-leroux448?

[isa-leroux448]

Sorry I forgot to request review again after Kevin fixed it. I've just resolved merge conflicts related to the sortable table columns. I've tested the table sorting and I think everything is working properly but might be worth a quick double-check on your end to make sure I didn't break anything.

[isa-leroux448]

@voctory bump that the PR is ready to review/merge (I don't wanna accumulate more merge conflicts lol)

[voctory]

I left one comment about the getNestedValue function if you could take a look, otherwise LGTM

[voctory]

What's the format of field? Wondering why field.split(".") is needed