Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Achievements Module #104

Open
wants to merge 11 commits into
base: main
Choose a base branch
from
Open

Add Achievements Module #104

wants to merge 11 commits into from

Conversation

nishant-nayak
Copy link
Member

@nishant-nayak nishant-nayak commented Jan 19, 2024

Description

Add achievements module.

Fixes #55.

Adding the achievements page to navbar is tracked in #135

Additionally addressed the following:

  • Removed @tailwindcss/forms and updated register/login form styles to use DaisyUI styling. This ensures consistent theming across all forms and also helps fix tabs. See here for more info.
  • Added a default length to GitHub username with GitHub's defined limit (39 characters)
  • Added a dev_accounts_db file which loads dev accounts for testing. Should be used ONLY in dev.
  • Updated title to mention IEEE NITK instead of Corpus

Dependencies

N/A

Type of Change

What types of changes does your code introduce?
Put an x in the boxes that apply

  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration. (for bug fix / breaking change)
Put an x in the boxes that apply

  • Test A
  • Test B

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

Copy link

render bot commented Jan 19, 2024

Copy link

livecycle bot commented Jan 19, 2024

ieee-nitk

Oops… We encountered errors building your playground 😕.
Check the logs here

Signed-off-by: Nishant Nayak <nishantnayak2001@gmail.com>
nishant-nayak and others added 6 commits January 19, 2024 23:00
Signed-off-by: Nishant Nayak <nishantnayak2001@gmail.com>
Signed-off-by: Nishant Nayak <nishantnayak2001@gmail.com>
Signed-off-by: Nishant Nayak <nishantnayak2001@gmail.com>
Signed-off-by: Nishant Nayak <nishantnayak2001@gmail.com>
Signed-off-by: Nishant Nayak <nishantnayak2001@gmail.com>
@nishant-nayak nishant-nayak marked this pull request as ready for review March 3, 2024 13:24
Signed-off-by: Nishant Nayak <nishantnayak2001@gmail.com>
nishant-nayak and others added 3 commits March 10, 2024 18:58
Signed-off-by: Nishant Nayak <nishantnayak2001@gmail.com>
Signed-off-by: Nishant Nayak <nishantnayak2001@gmail.com>
@nishant-nayak nishant-nayak marked this pull request as ready for review March 10, 2024 14:43
@nishant-nayak
Copy link
Member Author

image

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate Achievements Pages
1 participant