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
19 Replies
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
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>
Issue #790 by youssefjaziri456
[Feature]: New Design for User Profile Page
Is your feature request related to a problem? Please describe.
Objective:
To revamp the current User Profile page with a fresh design that enhances user experience and visual appeal.
Describe the solution you'd like
As discussed with @pranshugupta54 we propose a collaborative effort to brainstorm and implement a new design for the User Profile page. This will involve leveraging Figma to create mockups and sharing ideas to ensure a comprehensive redesign.
Alternatives
No response
Additional Context
Please feel free to provide any additional insights, suggestions, or concerns regarding the new design initiative
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
Issue #784 by rishita0205
[Feature]: Loading Screen for Home Page
Is your feature request related to a problem? Please describe.
while opening the main page the time required to load the whole page is quite noticeable and abrupt adding a loading screen can help
Describe the solution you'd like
Implement a loading screen on the main page
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
Issue #783 by Chaima-benyedder
[Bug]: Content becomes blurred when minimizing the dashboard page.
Contact Details
No response
What happened?
When consulting the dashboard page and then minimizing the Chrome browser window, the content on the dashboard becomes blurred. Upon maximizing the page, the content remains blurred, persisting even after restoring the browser window to its original size. This issue occurs consistently and affects the usability of the dashboard interface.
Steps to reproduce:
1. Navigate to the dashboard page.
2. Minimize the Chrome browser window.
3. Extract the drawer.
4. Maximize the browser window again.
!m
!b
!ma
What browsers are you seeing the problem on?
Chrome
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
Issue #781 by namnoum
[Feature]: Implement Contact Us Page
Is your feature request related to a problem? Please describe.
I propose adding a Contact Us page to the project's website. Currently, the "Contact Us" hyperlink in the footer redirects to the same page as the "About Us" hyperlink, with the link /about or /contact. However, I suggest creating a separate page where users can fill in their information, including their email address and a message they want to send to the team. Additionally, we can also add a link to join discord if it is the prefered way to contact.
Describe the solution you'd like
The Contact Us will be an accessible way to communicate with the project team. It serves as a platform for users to submit their inquiries, feedback, or any other messages they wish to convey.
Key components of new Page:
Header: The page will have a header section consistent with the overall design of the website.
Contact Form: The main component of the Contact Us page is the contact form. The form will include the following fields for users to fill out:
- Name: Users can input their name.
- Email Address: Users are required to provide their email address for the team to respond.
- Message: A text area where users can write their message or inquiry.
- Discord link(Optional): Including link to Digitomize discord page as a way to contact the team.
- Submit Button: A submit button at the bottom of the form allows users to send their message to the project team.
Footer: Similar to other pages on the website, the Contact Us page will have a footer section containing links to various resources, including links to the project's social media profiles, privacy policy, and terms of service.
Alternatives
No response
Additional Context
<img width="848" alt="Cap1" src="https://github.com/digitomize/digitomize/assets/97735329/dec8bd80-6bd4-4dc2-bfd2-d048995e06a7">
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
Issue #779 by Youssef-Elouedi
[Bug]: After Signup, loading screen doesn't disappear
Contact Details
mohamedyoussef.elouedi@medtech.tn
What happened?
After I successfully signing up, the loading screen appears but keeps loading without any action
What browsers are you seeing the problem on?
No response
Relevant log output
```shell
"api.js:68
GET http://localhost:4001/user/dashboard net::ERR_CONNECTION_REFUSED
dispatchXhrRequest @ chunk-B34HIOJJ.js?v=bdec4ee0:1513
xhr @ chunk-B34HIOJJ.js?v=bdec4ee0:1373
dispatchRequest @ chunk-B34HIOJJ.js?v=bdec4ee0:1590
_request @ chunk-B34HIOJJ.js?v=bdec4ee0:1872
request @ chunk-B34HIOJJ.js?v=bdec4ee0:1776
Axios.<computed> @ chunk-B34HIOJJ.js?v=bdec4ee0:1891
wrap @ chunk-B34HIOJJ.js?v=bdec4ee0:8
userDashboardDetails @ api.js:68
await in userDashboardDetails (async)
fetchData @ UserDashboard.jsx:149 (anonymous) @ UserDashboard.jsx:159 commitHookEffectListMount @ chunk-EL3ZTUGS.js?v=bdec4ee0:16904 commitPassiveMountOnFiber @ chunk-EL3ZTUGS.js?v=bdec4ee0:18152 commitPassiveMountEffects_complete @ chunk-EL3ZTUGS.js?v=bdec4ee0:18125 commitPassiveMountEffects_begin @ chunk-EL3ZTUGS.js?v=bdec4ee0:18115 commitPassiveMountEffects @ chunk-EL3ZTUGS.js?v=bdec4ee0:18105 flushPassiveEffectsImpl @ chunk-EL3ZTUGS.js?v=bdec4ee0:19486 flushPassiveEffects @ chunk-EL3ZTUGS.js?v=bdec4ee0:19443 (anonymous) @ chunk-EL3ZTUGS.js?v=bdec4ee0:19324 workLoop @ chunk-EL3ZTUGS.js?v=bdec4ee0:197 flushWork @ chunk-EL3ZTUGS.js?v=bdec4ee0:176 performWorkUntilDeadline @ chunk-EL3ZTUGS.js?v=bdec4ee0:384" "UserDashboard.jsx:140 Uncaught (in promise) TypeError: Failed to fetch at getContest (UserDashboard.jsx:140:30) at UserDashboard.jsx:144:5 at commitHookEffectListMount (chunk-EL3ZTUGS.js?v=bdec4ee0:16904:34) at invokePassiveEffectMountInDEV (chunk-EL3ZTUGS.js?v=bdec4ee0:18320:19) at invokeEffectsInDev (chunk-EL3ZTUGS.js?v=bdec4ee0:19697:19) at commitDoubleInvokeEffectsInDEV (chunk-EL3ZTUGS.js?v=bdec4ee0:19682:15) at flushPassiveEffectsImpl (chunk-EL3ZTUGS.js?v=bdec4ee0:19499:13) at flushPassiveEffects (chunk-EL3ZTUGS.js?v=bdec4ee0:19443:22) at performSyncWorkOnRoot (chunk-EL3ZTUGS.js?v=bdec4ee0:18864:11) at flushSyncCallbacks (chunk-EL3ZTUGS.js?v=bdec4ee0:9135:30) getContest @ UserDashboard.jsx:140 (anonymous) @ UserDashboard.jsx:144 commitHookEffectListMount @ chunk-EL3ZTUGS.js?v=bdec4ee0:16904 invokePassiveEffectMountInDEV @ chunk-EL3ZTUGS.js?v=bdec4ee0:18320 invokeEffectsInDev @ chunk-EL3ZTUGS.js?v=bdec4ee0:19697 commitDoubleInvokeEffectsInDEV @ chunk-EL3ZTUGS.js?v=bdec4ee0:19682 flushPassiveEffectsImpl @ chunk-EL3ZTUGS.js?v=bdec4ee0:19499 flushPassiveEffects @ chunk-EL3ZTUGS.js?v=bdec4ee0:19443 performSyncWorkOnRoot @ chunk-EL3ZTUGS.js?v=bdec4ee0:18864 flushSyncCallbacks @ chunk-EL3ZTUGS.js?v=bdec4ee0:9135 commitRootImpl @ chunk-EL3ZTUGS.js?v=bdec4ee0:19428 commitRoot @ chunk-EL3ZTUGS.js?v=bdec4ee0:19273 finishConcurrentRender @ chunk-EL3ZTUGS.js?v=bdec4ee0:18801 performConcurrentWorkOnRoot @ chunk-EL3ZT...
fetchData @ UserDashboard.jsx:149 (anonymous) @ UserDashboard.jsx:159 commitHookEffectListMount @ chunk-EL3ZTUGS.js?v=bdec4ee0:16904 commitPassiveMountOnFiber @ chunk-EL3ZTUGS.js?v=bdec4ee0:18152 commitPassiveMountEffects_complete @ chunk-EL3ZTUGS.js?v=bdec4ee0:18125 commitPassiveMountEffects_begin @ chunk-EL3ZTUGS.js?v=bdec4ee0:18115 commitPassiveMountEffects @ chunk-EL3ZTUGS.js?v=bdec4ee0:18105 flushPassiveEffectsImpl @ chunk-EL3ZTUGS.js?v=bdec4ee0:19486 flushPassiveEffects @ chunk-EL3ZTUGS.js?v=bdec4ee0:19443 (anonymous) @ chunk-EL3ZTUGS.js?v=bdec4ee0:19324 workLoop @ chunk-EL3ZTUGS.js?v=bdec4ee0:197 flushWork @ chunk-EL3ZTUGS.js?v=bdec4ee0:176 performWorkUntilDeadline @ chunk-EL3ZTUGS.js?v=bdec4ee0:384" "UserDashboard.jsx:140 Uncaught (in promise) TypeError: Failed to fetch at getContest (UserDashboard.jsx:140:30) at UserDashboard.jsx:144:5 at commitHookEffectListMount (chunk-EL3ZTUGS.js?v=bdec4ee0:16904:34) at invokePassiveEffectMountInDEV (chunk-EL3ZTUGS.js?v=bdec4ee0:18320:19) at invokeEffectsInDev (chunk-EL3ZTUGS.js?v=bdec4ee0:19697:19) at commitDoubleInvokeEffectsInDEV (chunk-EL3ZTUGS.js?v=bdec4ee0:19682:15) at flushPassiveEffectsImpl (chunk-EL3ZTUGS.js?v=bdec4ee0:19499:13) at flushPassiveEffects (chunk-EL3ZTUGS.js?v=bdec4ee0:19443:22) at performSyncWorkOnRoot (chunk-EL3ZTUGS.js?v=bdec4ee0:18864:11) at flushSyncCallbacks (chunk-EL3ZTUGS.js?v=bdec4ee0:9135:30) getContest @ UserDashboard.jsx:140 (anonymous) @ UserDashboard.jsx:144 commitHookEffectListMount @ chunk-EL3ZTUGS.js?v=bdec4ee0:16904 invokePassiveEffectMountInDEV @ chunk-EL3ZTUGS.js?v=bdec4ee0:18320 invokeEffectsInDev @ chunk-EL3ZTUGS.js?v=bdec4ee0:19697 commitDoubleInvokeEffectsInDEV @ chunk-EL3ZTUGS.js?v=bdec4ee0:19682 flushPassiveEffectsImpl @ chunk-EL3ZTUGS.js?v=bdec4ee0:19499 flushPassiveEffects @ chunk-EL3ZTUGS.js?v=bdec4ee0:19443 performSyncWorkOnRoot @ chunk-EL3ZTUGS.js?v=bdec4ee0:18864 flushSyncCallbacks @ chunk-EL3ZTUGS.js?v=bdec4ee0:9135 commitRootImpl @ chunk-EL3ZTUGS.js?v=bdec4ee0:19428 commitRoot @ chunk-EL3ZTUGS.js?v=bdec4ee0:19273 finishConcurrentRender @ chunk-EL3ZTUGS.js?v=bdec4ee0:18801 performConcurrentWorkOnRoot @ chunk-EL3ZT...
Issue #778 by Youssef-Elouedi
[Feature]: In the footer make the logo interactive for improved user experience
Is your feature request related to a problem? Please describe.
it's not related to a problem of functionality but convenience
Describe the solution you'd like
make the logo present in the footer interactive and directs the user to the home page
Alternatives
A method to redirect the user to the homepage is needed to ease the navigation and user experience
Additional Context
The main purpose of a website should be informative, easy to use and fast. This feature definitely improves on the ease of use and reduces time wasted by the user.
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
Issue #775 by Youssef-Elouedi
[Feature]: Error handling for createUserFirebase
Is your feature request related to a problem? Please describe.
while signing up in the dev environment, I encountered an error I couldn't figure out
Describe the solution you'd like
Implement a new error handling to improve the development process
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
Issue #772 by Youssef-Elouedi
[Feature]: Contest Sorting by Duration improvement
Is your feature request related to a problem? Please describe.
In the Contest page, the user is able to filter the search either by platform or duration. However, the filtering by duration is inefficient as most of the contests durations lie within the first percentile of the bar (below 240 min, except for two: 300 min and 11940min); this renders the filtering inefficient and makes the user confused
Describe the solution you'd like
A solution would be the user being able to filter either by hours for the long contests but that don't extend beyond days, by minutes if the user wants to find contests with a range of desired minutes. For the longer events/contests suggest the possibility to filter by number of days. (maybe two filtering options, the first is hours/minutes/days) and the second a slider is fine). We can also add the sorting feature
Alternatives
(maybe two filtering options, the first is hours/minutes/days) and the second a slider is fine). We can also add the sorting feature,
The user can maybe just sort them instead of sliding as it will be more efficient
Additional Context
!image
there is a 80-90% wasted slider as none of the contests are that long except maybe for one
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
Issue #764 by youssefjaziri456
[Bug]: account button
Contact Details
No response
What happened?
When I click on the account link that appears when logged in, or when I click on my profile picture, I encounter an error. Instead of being redirected to the expected page, an error is displayed.(I tried this on various accounts and different networks).
<img width="504" alt="Screenshot 2024-03-10 174235" src="https://github.com/digitomize/digitomize/assets/146774542/bcb0b157-0893-42e4-ac0e-0a5d3dab89d9">
What browsers are you seeing the problem on?
No response
Relevant log output
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
Issue #763 by namnoum
[Bug]: Drawer Bar Not Fully Scrollable in Normal Screen Mode
Contact Details
No response
What happened?
The drawer bar on the website is not scrollable to the end, causing content to be inaccessible. However, when viewing the website in full-screen mode you can see all options. Additionally, the chat option covers some of the content, making it impossible to read the text underneath.
Steps to reproduce:
1. Open the website in a browser.
2. Navigate to the Account page ( click in your image in the right of the screen)
3. Click on preferences.
4. Check the drawer in the left of the screen and attempt to scroll to the end of the drawer bar content.
5. Enter full-screen mode.
6. Observe that the content is cut off and cannot be accessed.
7. Notice that the chat option covers part of the content, making it unreadable.
8.
<img width="167" alt="1" src="https://github.com/digitomize/digitomize/assets/97735329/0f7dcac4-2e37-4f92-b756-bd07463cf50a">
This image shows how you can't scroll down the drawer when the screen is on normal mode
<img width="172" alt="Capture d’écran 2024-03-10 171944" src="https://github.com/digitomize/digitomize/assets/97735329/558fa751-2773-45d4-8d24-493b320bd9a2">
This image shows how the chat option covers the text.
What browsers are you seeing the problem on?
Others
Relevant log output
Are you interested in contributing?
- [X] I'd like to work on this issue
Code of Conduct
- [ ] I have used the search function to check if an issue already exists
- [X] I agree to follow this project's Code of Conduct
Issue #761 by pranshugupta54
[Feature]: Filters for hackathon
Is your feature request related to a problem? Please describe.
Implement filters like platform (devfolio, unstop etc), duration, city, month etc.
Describe the solution you'd like
.
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
Issue #754 by anuragdaksh7
[Bug]: text overflow in dashboard page on medium screen size
Contact Details
anuragdaksh77777@gmail.com
What happened?
I noticed text overflow on dashboard page when page size is near medium
!image
What browsers are you seeing the problem on?
Others
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
Issue #744 by dependabot[bot]
Bump husky from 8.0.3 to 9.0.11
Bumps husky from 8.0.3 to 9.0.11.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/typicode/husky/releases">husky's releases</a>.</em></p>
<blockquote>
<h2>v9.0.11</h2>
<ul>
<li>chore: update <code>package-lock.json</code> by <a href="https://github.com/btea"><code>@btea</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1383">typicode/husky#1383</a></li>
<li>fix: <code>export HUSKY=0</code> in init (fixes <a href="https://redirect.github.com/typicode/husky/issues/1393">#1393</a>) by <a href="https://github.com/typicode"><code>@typicode</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1395">typicode/husky#1395</a></li>
</ul>
<h2>v9.0.10</h2>
<ul>
<li>fix: rename index.d.ts to index.d.mts by <a href="https://github.com/mrkjdy"><code>@mrkjdy</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1379">typicode/husky#1379</a></li>
</ul>
<h2>v9.0.9</h2>
<ul>
<li>refactor: rename files by <a href="https://github.com/typicode"><code>@typicode</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1378">typicode/husky#1378</a></li>
</ul>
<h2>v9.0.8</h2>
<ul>
<li>docs: update index.md by <a href="https://github.com/khaledYS"><code>@khaledYS</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1369">typicode/husky#1369</a></li>
<li>Fix tab detection on install command by <a href="https://github.com/glensc"><code>@glensc</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1376">typicode/husky#1376</a></li>
<li>refactor: reduce file size by <a href="https://github.com/typicode"><code>@typicode</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1377">typicode/husky#1377</a></li>
</ul>
<h2>v9.0.7</h2>
<ul>
<li>fix: typo and source <code>~/.huskyrc</code> correctly (compatibility with v8)</li>
<li>docs: fix example by <a href="https://github.com/typicode"><code>@typicode</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1363">typicode/husky#1363</a></li>
</ul>
<h2>v9.0.6</h2>
<ul>
<li>docs: add favicon by <a href="https://github.com/rakleed"><code>@rakleed</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1354">typicode/husky#1354</a></li>
<li>chore: apply editorconfig to code only by <a href="https://github.com/typicode"><code>@typicode</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1355">typicode/husky#1355</a></li>
<li>docs: update install script to mjs and fix CI checks by <a href="https://github.com/starnayuta"><code>@starnayuta</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1357">typicode/husky#1357</a></li>
<li>Fix unbound variable by <a href="https://github.com/typicode"><code>@typicode</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1359">typicode/husky#1359</a></li>
</ul>
<h2>v9.0.5</h2>
<ul>
<li>docs: update path to ...