[WIP] Code Jam API

[JBraunsmaJr]

This PR is a WIP.

Implements #22

Showcase

Closes #22

[github-actions[bot]]

🦙 MegaLinter status: :warning: WARNING

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ CSHARP	dotnet-format	37	22	0	109.65s
✅ HTML	htmlhint	1		0	0.3s
✅ JSON	eslint-plugin-jsonc	3	0	0	1.01s
✅ JSON	prettier	3	3	0	0.7s
✅ JSON	v8r	3		0	3.25s
:warning: MARKDOWN	markdownlint	1	1	2	0.44s
✅ MARKDOWN	markdown-table-formatter	1	1	0	0.31s
✅ REPOSITORY	checkov	yes		no	9.77s
✅ REPOSITORY	gitleaks	yes		no	0.87s
✅ REPOSITORY	git_diff	yes		no	0.05s
✅ REPOSITORY	secretlint	yes		no	1.45s
✅ REPOSITORY	trivy	yes		no	3.35s
✅ SPELL	misspell	45	0	0	0.11s
✅ YAML	prettier	2	1	0	0.61s
✅ YAML	v8r	2		0	3.0s
✅ YAML	yamllint	2		0	0.26s

See errors details in artifact MegaLinter reports on CI Job page _Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff_

_MegaLinter is graciously provided by _

[JBraunsmaJr]

• Added a culture selector on the top right of appbar (we don't have a profile page/menu setup yet so this spot works for now?)
• Added Time Utility. Allows us to grab the timezone offset from the browser and apply that to whichever datetime value we want to view as "local time"

This will require standardization of all datetimes to use UTC. When displaying we can convert to local time using the new extension method.

[JBraunsmaJr]

Working on adding additional information to topic cards.

• Total solo applicants
• Total team applicants
• Ability to Withdraw (if already registered)
• Ability to register (if not registered)

[JBraunsmaJr]

• Added popover

When a user has not registered for a topic they'll see the register button as depicted below. We only have 1 parameter needed when registering (do you want to be on a team or be solo). Clicking the register button will bring up a popover menu with 2 icons that correlate to solo / team. Clicking one of those icons will send the appropriate request to register you.

[JBraunsmaJr]

Maybe add a bit of padding between Heading Topic 0,1,2,4 etc. Seems a bit bunched up with the picture. Thoughts?

Good call, shall add a smidge of padding in the next push

[JBraunsmaJr]

Added administrator icon to username display in the appbar -- should help a user know whether or not they are a standard user or not.

Certain topic actions such as delete were to be locked from general users... so adding the administrator ability was needed.

The first user to login becomes admin. Idea being, whoever sets this up for their community is 99% likely to be the community leader/owner anyhow. So it makes sense. They'll login to make sure stuff is working / setup before opening it up to general use.

Later we can add the ability for an admin to manage user roles

[JBraunsmaJr]

Added a dropdown navigational menu when user clicks on their username.

• if user has the admin role the Admin Portal will appear
• Otherwise, by default the account item will appear

[JBraunsmaJr]

The admin dashboard has the ability to manage topics. Right now this is what the tabled view looks like.

• Noticing MudBlazor does not implement the same "concept" of pagination as originally thought. They paginate a list of items already available versus having it fetch content from external source.

Added Scope

• Need to create a reusable pagination system which fetches data from our API.

[JBraunsmaJr]

Pagination Progress

Todo

• Need to figure out how to utilize Render Fragments so we can abstract this pagination component, make it even more reusable than reinventing the wheel every time
• Implement delete button functionality on the admin-topic page
• Add an edit/create topic section for admins as well

[JBraunsmaJr]

1. Didn't realize @typeparam was a valid directive in Blazor. This opened a lot of doors for us in terms of code reusability!
2. RenderFragments are our friends

[JBraunsmaJr]

Breaking Changes

• Migrated from MySQL to Postgres. Required regenerating migrations. Will require developers to run the reset-db powershell script we have. (Good thing we have that right? lol)
• Added GraphQL for enabling us to consolidate queries. Granted we're newbies with it so might take some time to standardize / get it right.

[JBraunsmaJr]

• Got Pagination working with GraphQL endpoint now
• Updated pagination models to be on the client side -- considering custom endpoints from server are no longer needed in this regard
• Removed unused methods/views/classes
• Added TotalCount to GraphQL query for the topics.
• Fixed problem where TopicID was not provided downstream
• Fixed problem where, I think, where Background image for topic cards were not appearing
• GraphQL related stuff is source generated from the schema file located in the Client directory. I'm not 100% certain how this works with auto-updating considering the project runs together. So -- if updates are made schema wise, just copy it from Banana Cake Pop and paste it in there.

[JBraunsmaJr]

Showcasing admin topic view when a topic is accepting applicants

This is the dialog that is able to both edit and create topics

As an administrator on the admin portal, one can add/edit/delete topics.