- Digitomize

Issue #738 by mrvivekthumar

Fixes #704, #705, #706 updated package,json file to latest version  Summary by CodeRabbit - Bug Fixes - Improved the readability and consistency of user data model by adjusting spacing and alignment in user properties.

19 Replies

DigitomizeOP•9mo ago

Issue #730 by mayankbaranwal0

Made terminal logs colorful Fixes #526 Enhanced terminal logs readability using picocolors by implementing a standard 4-color scheme - Red for Errors & warnings - Green for Successful outcome & task completion - Yellow for Caution & debugging info - Blue for Messages & general info  Summary by CodeRabbit - Refactor - Enhanced server console output with color-coded formatting for better readability and distinction.

DigitomizeOP•9mo ago

Issue #728 by SHUBH0924

[Bug]: Loading page button is not fixed Contact Details [email protected] What happened? In the loading page at the dashboard, buttons are not aligned with text properly. !image What browsers are you seeing the problem on? Chrome, Brave, edge Relevant log output No response Are you interested in contributing? - [x] I'd like to work on this issue Code of Conduct - [X] I have used the search function to check if an issue already exists - [X] I agree to follow this project's Code of Conduct

DigitomizeOP•9mo ago

Issue #706 by dependabot[bot]

DigitomizeOP•9mo ago

Issue #704 by dependabot[bot]

Bump prettier from 3.1.0 to 3.2.5 Bumps prettier from 3.1.0 to 3.2.5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/prettier/prettier/releases">prettier's releases</a>.</em></p> <blockquote> <h2>3.2.5</h2> <p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#325">Changelog</a></p> <h2>3.2.4</h2> <ul> <li>Fix <code>.eslintrc.json</code> format <a href="https://redirect.github.com/prettier/prettier/issues/15947">#15947</a></li> </ul> <p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#324">Changelog</a></p> <h2>3.2.3</h2> <ul> <li>Format <code>tsconfig.json</code> file with <code>jsonc</code> parser <a href="https://redirect.github.com/prettier/prettier/issues/15927">#15927</a></li> </ul> <p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#323">Changelog</a></p> <h2>3.2.2</h2> <p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#322">Changelog</a></p> <h2>3.2.1</h2> <p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#321">Changelog</a></p> <h2>3.2.0</h2> <p><a href="https://github.com/prettier/prettier/compare/3.1.1...3.2.0">diff</a></p> <p>🔗 <a href="https://prettier.io/blog/2024/01/12/3.2.0.html">Release note</a></p> <h2>3.1.1</h2> <p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#311">Changelog</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md">prettier's changelog</a>.</em></p> <blockquote> <h1>3.2.5</h1> <p><a href="https://github.com/prettier/prettier/compare/3.2.4...3.2.5">diff</a></p> <h4>Support Angular inline styles as single template literal (<a href="https://redirect.github.com/prettier/prettier/pull/15968">#15968</a> by <a href="https://github.com/sosukesuzuki"><code>@sosukesuzuki</code></a>)</h4> <p><a href="https://blog.angular.io/introducing-angular-v17-4d7033312e4b">Angular v17</a> supports single string inline styles.</p>  <pre lang="ts"><code>// Input @Component({ template: <div>...</div>, styles: h1 { color: blue; }, }) export class AppComponent {} <p>// Prettier 3.2.4 <a href="https://github.com/Component"><code>@Component</code></a>({ template: <code>&lt;div&gt;...&lt;/div&gt;</code>, styles: <code>h1 { color: blue; }</code>, }) export class AppComponent {}</p> <p>// Prettier 3.2.5 <a href="https://github.com/Component"><code>@Component</code></a>({ template: <code>&lt;div&gt;...&lt;/div&gt;</code>, styles: <code>h1 { color: blue; }</code>, }) export class AppComponent {}</p> <p></code></pre></p> <h4>Unexpected embedded formatting for Angular template (<a href="https://redirect.github.com/prettier/prettier/pull/15969">#15969</a> by <a href="https://github.com/JounQin"><code>@JounQin</code></a>)</h4> <p>Computed template should not be considered as A...

DigitomizeOP•9mo ago

Issue #588 by jaydeep203

feature: Signup or Login modal added Feature #532 I have created a login/signup modal in client/components/modals . I have added it currently in the leaderboard section of the website; if the user is not logged in, it gets triggered in the useEffect hook. I have created a src/hooks/useLoginModal.ts file to control the open and close of the modal using zustand. Use the modal wherever you want in the app. I have not tested it in the backend because I only updated the frontend.  Summary by CodeRabbit - New Features - Introduced a modal component for user authentication and registration, supporting both traditional and social (Google, GitHub) login methods. - Added a custom React hook for managing the visibility of the login modal. - Chores - Updated the .gitignore file for better file management in version control. - Enhancements - Integrated the new authentication modal into the Leaderboard feature, prompting users to log in or register to view leaderboard details.

DigitomizeOP•9mo ago

Issue #581 by Manishak798

[Feature]: Re-designing of the Card and inserting API fetched User Details Is your feature request related to a problem? Please describe. As a viewer, these cards don't showcase any information at all that would help the visitors, we can consider restyling the card elements and to make it more readable we can insert dynamic card values through JS API or we can create our user API. Describe the solution you'd like By using javascript and CSS for this we can achieve desired results for the same. Alternatives No response Additional Context !Screenshot 2024-01-28 170013 Are you interested in contributing? - [ ] I'd like to work on this issue Code of Conduct - [X] I have used the search function to check if an issue already exists - [X] I agree to follow this project's Code of Conduct

DigitomizeOP•9mo ago

Issue #580 by Manishak798

[Feature]: Redesigning of this user Card Is your feature request related to a problem? Please describe. Re-Designing this to create a new user card will make the website look more appealing to the users. Describe the solution you'd like The solution to this is to do restyling of elements and adding js to the input tag to remove their input value when the page refreshes. Alternatives As a SWOC mentor, I am raising this issue for contributors. Additional Context !Screenshot 2024-01-28 165927 Are you interested in contributing? - [ ] I'd like to work on this issue Code of Conduct - [X] I have used the search function to check if an issue already exists - [X] I agree to follow this project's Code of Conduct

DigitomizeOP•9mo ago

Issue #566 by Ajen07

feat: Send verification email fixes #538 It sends verification email to users signingup using email and password using firebase  Summary by CodeRabbit - New Features - Enhanced email verification process, including the ability to resend verification emails. - Added toast notifications for successful actions. - Updated authentication flow to include email verification checks. - Bug Fixes - Improved password visibility toggle functionality. - Refactor - Updated navigation and authentication logic across several components for a smoother user experience. - Style - Introduced new styles for the email verification components, ensuring responsive design. - Chores - Minor UI adjustments and comment updates for clarity.

DigitomizeOP•9mo ago

Issue #538 by pranshugupta54

[Bug]: Email verification on signup Contact Details No response What happened? There is no verification when user signs up using email - Use email verification with firebase - info. - Also implement a check for all authorised page to redirect to login page with message as "Verify your email address first" What browsers are you seeing the problem on? No response Relevant log output No response Are you interested in contributing? - [ ] I'd like to work on this issue Code of Conduct - [X] I have used the search function to check if an issue already exists - [X] I agree to follow this project's Code of Conduct

DigitomizeOP•9mo ago

Issue #537 by pranshugupta54

[Feature]: Programs section on About Page Is your feature request related to a problem? Please describe. include program list like swoc kwoc etc Describe the solution you'd like On the about page, make a section for programs using react marquee, which shows all the programs we're a part of. - KWOC - SWOC - Tublian - IWOC Alternatives No response Additional Context Include their images (prefer svg) and date below it. Are you interested in contributing? - [ ] I'd like to work on this issue Code of Conduct - [X] I have used the search function to check if an issue already exists - [X] I agree to follow this project's Code of Conduct

DigitomizeOP•9mo ago

Issue #536 by Parmesh119

[Feature]: Contact Us page in official website Is your feature request related to a problem? Please describe. In this official website, there is a contact us page but the contact us page doesn't exist. Describe the solution you'd like I would like to make the new contact us form with already mentioned information in website. Alternatives No response Additional Context No response Are you interested in contributing? - [X] I'd like to work on this issue Code of Conduct - [X] I have used the search function to check if an issue already exists - [X] I agree to follow this project's Code of Conduct

DigitomizeOP•9mo ago

Issue #532 by pranshugupta54

[Feature]: Signup/Login Modal Is your feature request related to a problem? Please describe. Currently, our user authentication process involves redirecting users to a separate signup/login page, which may disrupt the user experience and flow. It would be beneficial to have a more seamless approach by introducing a signup/login modal that can be prompted at various places throughout the application. Describe the solution you'd like Introduce a feature that allows the integration of a signup/login modal, which can be triggered from multiple points within the application. This will enhance user convenience and provide a more streamlined experience without the need for redirects. Alternatives No response Additional Context - Modal Component: Create a reusable modal component that includes signup and login forms. - Integration Points: Implement the modal trigger at various locations within the application, such as navigation bars, buttons, or other relevant UI elements. - Flexibility: Ensure the modal can be easily customized and configured to meet the design and branding requirements of different sections of the application. Are you interested in contributing? - [ ] I'd like to work on this issue Code of Conduct - [X] I have used the search function to check if an issue already exists - [X] I agree to follow this project's Code of Conduct

DigitomizeOP•9mo ago

Issue #529 by pranshugupta54

[Feature]: Implement Webhook logging Is your feature request related to a problem? Please describe. NA Describe the solution you'd like Add webhook logging on discord for more events. Currently it's only for User Created and User Update. Alternatives No response Additional Context NOTE: This is a major feature, will require more time and information about the backend. Are you interested in contributing? - [ ] I'd like to work on this issue Code of Conduct - [X] I have used the search function to check if an issue already exists - [X] I agree to follow this project's Code of Conduct

DigitomizeOP•9mo ago

Issue #526 by pranshugupta54

[DIG-119] [Feature]: [EASY] Make terminal logs colourful Is your feature request related to a problem? Please describe. The terminal for backend looks very plain. Describe the solution you'd like Can use picocolors to make them look cool !image Alternatives No response Additional Context Don't use too much of formatting, just make it look better and easier to understand. Can make similar things of same color etc. Are you interested in contributing? - [ ] I'd like to work on this issue Code of Conduct - [X] I have used the search function to check if an issue already exists - [X] I agree to follow this project's Code of Conduct <sub>From SyncLinear.com | DIG-119</sub>

DigitomizeOP•9mo ago

Issue #521 by pranshugupta54

[DIG-118] [Feature]: Subscribe to Blogs Is your feature request related to a problem? Please describe. New Signups automatically get signup for blogs. Describe the solution you'd like On the Signup Page, we can add a checkbox (which is ticked by default). This automatically adds to the user to our hashnode blog newsletter. Alternatives No response Additional Context Explore hashnode yourself - here Are you interested in contributing? - [ ] I'd like to work on this issue Code of Conduct - [X] I have used the search function to check if an issue already exists - [X] I agree to follow this project's Code of Conduct <sub>From SyncLinear.com | DIG-118</sub>

DigitomizeOP•9mo ago

Issue #519 by Chakit22

Added a feature for skills input field section. 1. Introduced a mechanism that triggers a toast error message when the character limit in an input field is exceeded, even before the user clicks on the submit button. 2. In this way users will receive immediate feedback when trying to input the 26th character, reducing confusion and frustration  Summary by CodeRabbit - New Features - Implemented input validation for skill entries on the user dashboard, limiting input to 25 characters and providing user feedback if exceeded.

DigitomizeOP•9mo ago

Issue #518 by Chakit22

[Feature]: Character Limit on skills input field Is your feature request related to a problem? Please describe. I propose the implementation of a feature that enhances user experience by providing real-time feedback on character limits in an input field in the skills section. Currently, the user may encounter confusion when attempting to input more than 25 characters without knowing there is a limit until submission. Describe the solution you'd like I would like to request a feature that raises a toast error if the character limit in the input field exceeds 25 characters, even before the user clicks on Add. This would enhance the user experience by preventing confusion when trying to enter the 26th character in the skills section. This prevents confusion for users when attempting to enter more than 25 characters. This also enhances user awareness of character limits before adding a skill. Users will receive immediate feedback when trying to input the 26th character, reducing confusion and frustration. Alternatives No response Additional Context No response Are you interested in contributing? - [X] I'd like to work on this issue Code of Conduct - [X] I have used the search function to check if an issue already exists - [X] I agree to follow this project's Code of Conduct

DigitomizeOP•9mo ago

Issue #511 by mendacium-a11y

[DIG-116][Bug]: Add pre-commit hook to check for linting mistakes Contact Details No response What happened? implement a pre-commit hook that runs the eslint script in the root of the folder to check for linting problems What browsers are you seeing the problem on? No response Relevant log output No response Are you interested in contributing? - [ ] I'd like to work on this issue Code of Conduct - [X] I have used the search function to check if an issue already exists - [X] I agree to follow this project's Code of Conduct

DigitomizeOP•9mo ago

Issue #510 by pranshugupta54

[DIG-116] [Feature]: Implement query based contests Is your feature request related to a problem? Please describe. Current State: Our contests page currently features a dropdown filter for users to select specific platforms. While this has been functional, there is a growing need to provide users with more flexibility and a quicker way to access contests based on their preferences. Describe the solution you'd like Requested Enhancement: We propose implementing query-based filtering for the contests page, allowing users to specify their preferred platforms directly in the URL. This would enhance the user experience and provide a more dynamic way of accessing relevant contest information. Desired Functionality: - Users should be able to filter contests by appending query parameters to the URL. - Example: https://digitomize.com/contests?platform=leetcode - Additionally, users should be able to filter by multiple platforms, separating them with commas. - Example: https://digitomize.com/contests?platform=leetcode,codechef Alternatives No response Additional Context No response Are you interested in contributing? - [ ] I'd like to work on this issue Code of Conduct - [X] I have used the search function to check if an issue already exists - [X] I agree to follow this project's Code of Conduct <sub>DIG-116</sub>

Gaming

Programming