Issue #566 by Ajen07
feat: Send verification email
fixes #538
It sends verification email to users signingup using email and password using firebase
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
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.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
19 Replies
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
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
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
Issue #1038 by dependabot[bot]
Bump the npm_and_yarn group across 3 directories with 4 updates
Bumps the npm_and_yarn group with 3 updates in the /backend directory: @grpc/grpc-js, braces and ws.
Bumps the npm_and_yarn group with 4 updates in the /client directory: @grpc/grpc-js, braces, ws and engine.io-client.
Bumps the npm_and_yarn group with 2 updates in the /extension/contest_list directory: braces and ws.
Updates
@grpc/grpc-js from 1.10.7 to 1.10.9
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/grpc/grpc-node/releases"><code>@grpc/grpc-js</code>'s releases</a>.</em></p>
<blockquote>
<h2><code>@grpc/grpc-js</code> 1.10.9</h2>
<ul>
<li>Avoid buffering significantly more than <code>grpc.max_receive_message_size</code> per received message.</li>
</ul>
<h2><code>@grpc/grpc-js</code> 1.10.8</h2>
<ul>
<li>Fix a bug that caused channels with <code>unix:</code> targets to not reconnect after the channel goes idle (<a href="https://redirect.github.com/grpc/grpc-node/issues/2750">#2750</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/grpc/grpc-node/commit/674f4e351a619fd4532f84ae6dff96b8ee4e1ed3"><code>674f4e3</code></a> Merge pull request from GHSA-7v5v-9h63-cj86</li>
<li><a href="https://github.com/grpc/grpc-node/commit/7ecaa2d2dcaaa49467d41143169212caf55a40cd"><code>7ecaa2d</code></a> grpc-js: Bump to 1.10.9</li>
<li><a href="https://github.com/grpc/grpc-node/commit/e64d816d7df6d6cde62314beb67d11f1e0a8c79e"><code>e64d816</code></a> grpc-js: Avoid buffering significantly more than max_receive_message_size per...</li>
<li><a href="https://github.com/grpc/grpc-node/commit/45e5fe5462fea6cb4e3898fa2f07a4836f95916a"><code>45e5fe5</code></a> Merge pull request <a href="https://redirect.github.com/grpc/grpc-node/issues/2750">#2750</a> from murgatroid99/grpc-js_idle_uds_fix</li>
<li><a href="https://github.com/grpc/grpc-node/commit/87a35414021f627f01591cade9b1f9a7dcaaf5d3"><code>87a3541</code></a> grpc-js: Fix UDS channels not reconnecting after going idle</li>
<li><a href="https://github.com/grpc/grpc-node/commit/3105791fbe8a615a28289da33ad584fb868d2ff6"><code>3105791</code></a> Merge pull request <a href="https://redirect.github.com/grpc/grpc-node/issues/2740">#2740</a> from sergiitk/backport-1.10-psm-interop-common-prod-...</li>
<li><a href="https://github.com/grpc/grpc-node/commit/fec135a9800ce884b8dd414782f4bd0014821a0c"><code>fec135a</code></a> Merge pull request <a href="https://redirect.github.com/grpc/grpc-node/issues/2729">#2729</a> from sergiitk/psm-interop-common-prod-tests</li>
<li><a href="https://github.com/grpc/grpc-node/commit/76fe802309ff39c79887d494760de25633b2beb1"><code...Issue #1037 by dependabot[bot]
Bump the npm_and_yarn group across 3 directories with 3 updates
Bumps the npm_and_yarn group with 2 updates in the /backend directory: @grpc/grpc-js and ws.
Bumps the npm_and_yarn group with 3 updates in the /client directory: @grpc/grpc-js, ws and engine.io-client.
Bumps the npm_and_yarn group with 1 update in the /extension/contest_list directory: ws.
Updates
@grpc/grpc-js from 1.10.7 to 1.10.9
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/grpc/grpc-node/releases"><code>@grpc/grpc-js</code>'s releases</a>.</em></p>
<blockquote>
<h2><code>@grpc/grpc-js</code> 1.10.9</h2>
<ul>
<li>Avoid buffering significantly more than <code>grpc.max_receive_message_size</code> per received message.</li>
</ul>
<h2><code>@grpc/grpc-js</code> 1.10.8</h2>
<ul>
<li>Fix a bug that caused channels with <code>unix:</code> targets to not reconnect after the channel goes idle (<a href="https://redirect.github.com/grpc/grpc-node/issues/2750">#2750</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/grpc/grpc-node/commit/674f4e351a619fd4532f84ae6dff96b8ee4e1ed3"><code>674f4e3</code></a> Merge pull request from GHSA-7v5v-9h63-cj86</li>
<li><a href="https://github.com/grpc/grpc-node/commit/7ecaa2d2dcaaa49467d41143169212caf55a40cd"><code>7ecaa2d</code></a> grpc-js: Bump to 1.10.9</li>
<li><a href="https://github.com/grpc/grpc-node/commit/e64d816d7df6d6cde62314beb67d11f1e0a8c79e"><code>e64d816</code></a> grpc-js: Avoid buffering significantly more than max_receive_message_size per...</li>
<li><a href="https://github.com/grpc/grpc-node/commit/45e5fe5462fea6cb4e3898fa2f07a4836f95916a"><code>45e5fe5</code></a> Merge pull request <a href="https://redirect.github.com/grpc/grpc-node/issues/2750">#2750</a> from murgatroid99/grpc-js_idle_uds_fix</li>
<li><a href="https://github.com/grpc/grpc-node/commit/87a35414021f627f01591cade9b1f9a7dcaaf5d3"><code>87a3541</code></a> grpc-js: Fix UDS channels not reconnecting after going idle</li>
<li><a href="https://github.com/grpc/grpc-node/commit/3105791fbe8a615a28289da33ad584fb868d2ff6"><code>3105791</code></a> Merge pull request <a href="https://redirect.github.com/grpc/grpc-node/issues/2740">#2740</a> from sergiitk/backport-1.10-psm-interop-common-prod-...</li>
<li><a href="https://github.com/grpc/grpc-node/commit/fec135a9800ce884b8dd414782f4bd0014821a0c"><code>fec135a</code></a> Merge pull request <a href="https://redirect.github.com/grpc/grpc-node/issues/2729">#2729</a> from sergiitk/psm-interop-common-prod-tests</li>
<li><a href="https://github.com/grpc/grpc-node/commit/76fe802309ff39c79887d494760de25633b2beb1"><code>76fe802</code></a> Merge pull request <a href="https://redirect.github.com/grpc/grpc-node/issues/2739">#2739</a> from murgatroid99/backport-1.10-gr...Issue #1035 by dependabot[bot]
Bump prettier from 3.1.0 to 3.3.2
Bumps prettier from 3.1.0 to 3.3.2.
<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.3.2</h2>
<p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#332">Changelog</a></p>
<h2>3.3.1</h2>
<p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#331">Changelog</a></p>
<h2>3.3.0</h2>
<p><a href="https://github.com/prettier/prettier/compare/3.2.5...3.3.0">diff</a></p>
<p>🔗 <a href="https://prettier.io/blog/2024/06/01/3.3.0.html">Release note</a></p>
<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.3.2</h1>
<p><a href="https://github.com/prettier/prettier/compare/3.3.1...3.3.2">diff</a></p>
<h4>Fix handlebars path expressions starts with <code>@</code> (<a href="https://redirect.github.com/prettier/prettier/pull/16358">#16358</a> by <a href="https://github.com/Princeyadav05"><code>@Princeyadav05</code></a>)</h4>
<!-- raw HTML omitted -->
<pre lang="hbs"><code>{{! Input }}
<div>{{@x.y.z}}</div>
<p>{{! Prettier 3.3.1 }}
<div>{{<a href="https://github.com/x"><code>@x</code></a>}}</div></p>
<p>{{! Prettier 3.3.2 }}
<div>{{<a href="https://github.com/x"><code>@x</code></a>.y.z}}</div>
</code></pre></p>
<h1>3.3.1</h1>
<p><a href="https://github.com/prettier/prettier/compare/3.3.0...3.3.1">diff</a></p>
<h4>Preserve empty lines in front matter (<a href="https://redirect.github.com/prettier/prettier/pull/16347">#16347</a> by <a href="https://github.com/fisker"><code>@fisker</code></a>)</h4>
<!-- raw HTML omitted -->...
Issue #1034 by AkhilaSunesh
[Feature]: Add facility to view the password
Is your feature request related to a problem? Please describe.
!image
Location: Login and sign up page
Makes it easy for the users to view the password
Describe the solution you'd like
Professional outlook
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
Which program are you contributing in?
gssoc
Issue #1033 by thevijayshankersharma
[Feature]: Automatic Comment on Pull Request Raised
Is your feature request related to a problem? Please describe.
Often, when pull requests (PRs) are raised, reviewers may lack crucial context about the changes proposed. This can lead to delays in the review process and misunderstandings between contributors and reviewers.
Describe the solution you'd like
I propose implementing an automatic commenting system that triggers whenever a new PR is raised. This system would generate a predefined comment containing essential context about the changes, such as the purpose of the modifications, relevant issue or feature IDs, and specific instructions for reviewers.
Alternatives
One alternative could be relying solely on manual comments by reviewers upon PR creation. However, this approach may be time-consuming and inconsistent across different reviewers. Another option could be not providing any initial comments on PRs, but this would result in contributors having to repeatedly provide context to reviewers, slowing down the review process.
Additional Context
Automating the commenting process upon PR creation would streamline the review process, improve communication between contributors and reviewers, and ultimately enhance the efficiency and effectiveness of our project's development workflow.
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
Which program are you contributing in?
gssoc, ssoc
Issue #1032 by Abdullah-Usmani1994
[Feature]: Open Blogs in a New Tab in Digitomize
Is your feature request related to a problem? Please describe.
When a user clicks on a blogs link within the Digitomize application, the blog opens in the same tab, causing the previous page to disappear.
Describe the solution you'd like
When a user clicks on a blogs link, it should open in a new tab, allowing the user to keep the current page open while accessing the blog in a separate tab.
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
Which program are you contributing in?
Not applicable
Issue #1031 by Aadithya-J
[Feature]: Change challenge to use the backend api
Is your feature request related to a problem? Please describe.
the challenge from quine is being displayed manually but the backend is added now.
Describe the solution you'd like
i want to modfiy the frontend to use the backend api to display the challenge
Alternatives
No response
Additional Context
PR is made for backend https://github.com/digitomize/digitomize/pull/1030
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
Which program are you contributing in?
gssoc
Issue #1030 by Aadithya-J
feat: backend for challenges
Pull Request Details
Description
Implemented backend which fetches challenge from quine quests. according to issue 836
Type of PR
- [x] Feature enhancement
Summary
-added controller to fetch challenge from quine using axios
-setup routes and mongoose model for the challenge
-setup index.js to update db and sync regularly for the challenges
Screenshots (if applicable)
<img width="862" alt="Screenshot 2024-06-11 at 9 24 48 PM" src="https://github.com/digitomize/digitomize/assets/147314019/9b4f1c98-f1d0-4240-82de-cc7a5c3341d7">
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Introduced functionality to fetch, update, and sync challenges from MongoDB and an external API.
- Added route for fetching a list of challenges and returning it as JSON.
- Implemented a MongoDB schema for challenges with necessary fields and validations.
- Enhancements
- Improved error handling for challenge data retrieval and synchronization processes.
- Integrations
- Integrated new functions to update and sync challenges, and set up challenge routes for handling requests in both production and development environments.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Issue #1025 by harmeetsingh11
[Feature]: Animate Contest Page Using
Framer-Motion Library
Is your feature request related to a problem? Please describe.
The home page is currently animated, but the contest page lacks similar animations. To provide a consistent and engaging user experience, the contest page should be animated using the Framer-Motion library. This includes animating all elements such as headings, contest cards, tags, etc., similar to the animations on the home page.
Feature Requirements:
- Use the Framer-Motion library to add animations to the contest page.
- Animate the following elements:
- Headings
- Contest cards
- Tags
- Any other relevant elements
Expected Behavior:
The contest page should have smooth animations similar to those on the home page, enhancing the visual appeal and user experience.
Current Behavior:
The contest page is static and lacks animations, which creates an inconsistent experience compared to the animated home page.
Describe the solution you'd like
- Integrate the Framer-Motion library into the contest page.
- Implement animations for all specified elements, ensuring they are consistent with the home page animations.
Alternatives
No response
Additional Context
- The animations on the contest page should mirror the style and feel of the home page animations.
- Ensure that the animations do not impact the page's performance negatively.
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
Which program are you contributing in?
ssoc'24Issue #1024 by harmeetsingh11
[Bug]: Console Errors and Debug Information Displayed on Contest Page Load and Scroll
Contact Details
No response
What happened?
When the contest page is loaded and scrolled, there are various errors, objects, and other debug information displayed in the browser console. This is a bug that needs to be fixed as exposing such information in production code is not advisable.
Steps to Reproduce:
1. Navigate to the contest page.
2. Open the browser console (usually accessible via F12 or right-click > Inspect > Console).
3. Scroll through the contest page.
4. Observe the errors and debug information appearing in the console.
Expected Behavior:
No errors or debug information should be displayed in the browser console during the loading and scrolling of the contest page.
Actual Behavior:
Errors and debug information are displayed in the browser console when the contest page is loaded and scrolled.
Screenshots:
!Screenshot 2024-06-09 221637
Possible Solution:
- Ensure that all debug information and error logs are removed or handled appropriately in the production environment.
- Implement proper error handling to avoid exposing sensitive information.
What browsers are you seeing the problem on?
Others
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
Which program are you contributing in?
ssoc'24
Issue #1023 by vinayak-vohra
fix: update button state on successful login and signup
Pull Request Details
Description
Moved the
setbtnState() from catch block to finally block thus updating the button state in both success and error flows.
Fixes
fixes #939
Type of PR
- [x] Bug fix
- [ ] Feature enhancement
- [ ] Documentation update
- [ ] Refactoring
- [ ] Other (specify): ___
Checklist
- [x] I have read and followed the Pull Requests and Issues guidelines.
- [ ] The code has been properly linted and formatted using npm run lint:fix and npm run format:fix.
- [x] I have tested the changes thoroughly before submitting this pull request.
- [x] I have provided relevant issue numbers, snapshots, and videos after making the changes.
- [x] I have not borrowed code without disclosing it, if applicable.
- [x] This pull request is not a Work In Progress (WIP), and only completed and tested changes are included.
- [x] I have tested these changes locally.
- [x] My code follows the project's style guidelines.
- [ ] I have updated the documentation accordingly.
- [x] This PR has a corresponding issue in the issue tracker.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- Bug Fixes
- Improved reliability of login and signup button states by ensuring they reset correctly regardless of the outcome.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->Issue #1022 by chandannekya
[Feature]: Adding email Validation
Is your feature request related to a problem? Please describe.
At this point, users can register with any email, which may lead to threats.
Describe the solution you'd like
There should be a process that validates the email so only valid users can register.
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
Which program are you contributing in?
gssoc
Issue #1018 by TheMarvelFan
Implementing Backend Route for Statistics Update
Pull Request Details
Description
[Provide a brief overview of the changes introduced by this pull request.]
Fixes #341
[Cite any related issues or bugs that this PR addresses, e.g., "Fixes #issueNumber"]
Type of PR
- [ ] Bug fix
- [x] Feature enhancement
- [ ] Documentation update
- [x] Refactoring
- [ ] Other (specify): ___
Summary
[Summarize the changes made in this PR.]
Screenshots (if applicable)
[If your changes include UI updates, provide screenshots to illustrate the changes.]
Additional Notes
[Include any additional information or context that might be helpful for reviewers.]
Checklist
- [x] I have read and followed the Pull Requests and Issues guidelines.
- [x] The code has been properly linted and formatted using
npm run lint:fix and npm run format:fix.
- [x] I have tested the changes thoroughly before submitting this pull request.
- [x] I have provided relevant issue numbers, snapshots, and videos after making the changes.
- [x] I have not borrowed code without disclosing it, if applicable.
- [x] This pull request is not a Work In Progress (WIP), and only completed and tested changes are included.
- [x] I have tested these changes locally.
- [x] My code follows the project's style guidelines.
- [ ] I have updated the documentation accordingly.
- [x] This PR has a corresponding issue in the issue tracker.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Introduced an API endpoint to retrieve contributors' statistics from GitHub.
- Added scheduled updates to fetch and store contributors' data.
- Chores
- Updated dependencies in package.json to include axios, node-cron, sequelize, and sqlite3.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->Issue #1017 by Latish705
fix: Need improvement in auth modal
Pull Request Details
Description
improved the performance of auth modal which was starting first time not in shape by using callback hook of react which Memoizing these functions can help avoid unnecessary re-renders and side effects.
Fixes
fixes - #1005
Type of PR
- [x] Bug fix
- [ ] Feature enhancement
- [ ] Documentation update
- [ ] Refactoring
- [ ] Other (specify): ___
Summary
Screenshots (if applicable)
https://github.com/digitomize/digitomize/assets/104522651/1f86453a-6ba7-4b73-b687-eee2c0e3a78a
Checklist
- [x] I have read and followed the Pull Requests and Issues guidelines.
- [x] The code has been properly linted and formatted using
npm run lint:fix and npm run format:fix.
- [x] I have tested the changes thoroughly before submitting this pull request.
- [x] I have provided relevant issue numbers, snapshots, and videos after making the changes.
- [x] I have not borrowed code without disclosing it, if applicable.
- [x] This pull request is not a Work In Progress (WIP), and only completed and tested changes are included.
- [x] I have tested these changes locally.
- [x] My code follows the project's style guidelines.
- [x] I have updated the documentation accordingly.
- [x] This PR has a corresponding issue in the issue tracker.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- Refactor
- Improved performance and efficiency of the authentication modal by optimizing event handlers and state updates.
- Enhanced modal interaction by ensuring it closes when clicking outside of it.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->Issue #1012 by harshitjaglan
feat: Addedfollowing pointer on Homepage (PR #856)
Pull Request Details
Description
To make the website more appealing I used user's avatar on homepage to pop up when hovered over a specific area.
Fixes
PR #856
Type of PR
- [ ] Bug fix
- [x] Feature enhancement
- [ ] Documentation update
- [ ] Refactoring
- [ ] Other (specify): ___
Summary
Added the feature to see your name and avatar when your cursor is over a specific area.
Screenshots (if applicable)
<img width="1033" alt="Screenshot 2024-06-05 at 12 05 45 AM" src="https://github.com/digitomize/digitomize/assets/116933487/314ed19c-0d9d-43be-82a5-d6d50b6ff322">
Additional Notes
- Dependencies installed:
npm i framer-motion clsx tailwind-merge
npm install random-avatar-generator
npm install unique-names-generator
- Also I linted the codebase
Checklist - [x] I have read and followed the Pull Requests and Issues guidelines. - [x] The code has been properly linted and formatted using
npm install unique-names-generator
- Also I linted the codebase
Checklist - [x] I have read and followed the Pull Requests and Issues guidelines. - [x] The code has been properly linted and formatted using
npm run lint:fix and npm run format:fix.
- [x] I have tested the changes thoroughly before submitting this pull request.
- [x] I have provided relevant issue numbers, snapshots, and videos after making the changes.
- [x] I have not borrowed code without disclosing it, if applicable.
- [x] This pull request is not a Work In Progress (WIP), and only completed and tested changes are included.
- [x] I have tested these changes locally.
- [x] My code follows the project's style guidelines.
- [x] I have updated the documentation accordingly.
- [x] This PR has a corresponding issue in the issue tracker.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Introduced a follow pointer card component that tracks mouse movements and displays dynamic content on the home page.
- Added utility functions for combining class names and dynamic Tailwind CSS configurations.
- Enhancements
- Improved code readability, consistency, and formatting across multiple backend controllers and models.
- Enhanced error handling mechanisms in various backend controllers.
- Updated and added new dependencies in the client package.
- Bug Fixes
- Corrected indentation, spacing, and syntax errors in multiple backend files to ensure better code quality and maintainability.
- Refactor
- Refactored several backend controllers for better structure and readability.
- Reordered properties and adjusted formatting in various backend models and utility files.
- Style
- Adjusted formatting, added semicolons, and improved code alignment in several backend files.
- Chores
- Updated Tailwind CSS configuration to include new properties and dynamic color handling functions.
- Added new dependencies to the client package for avatar...Issue #1011 by RamakrushnaBiswal
feat: Required logos added in the supported by section
Pull Request Details
Description
Rwquired logos added in the supported by section
Fixes
#989 solved
Type of PR
- [x] Bug fix
- [x] Feature enhancement
- [ ] Documentation update
- [ ] Refactoring
- [ ] Other (specify): ___
Summary
[Summarize the changes made in this PR.]
Screenshots (if applicable)
!image
Additional Notes
[Include any additional information or context that might be helpful for reviewers.]
Checklist
- [x] I have read and followed the Pull Requests and Issues guidelines.
- [x] The code has been properly linted and formatted using
npm run lint:fix and npm run format:fix.
- [x] I have tested the changes thoroughly before submitting this pull request.
- [x] I have provided relevant issue numbers, snapshots, and videos after making the changes.
- [x] I have not borrowed code without disclosing it, if applicable.
- [x] This pull request is not a Work In Progress (WIP), and only completed and tested changes are included.
- [x] I have tested these changes locally.
- [x] My code follows the project's style guidelines.
- [x] I have updated the documentation accordingly.
- [x] This PR has a corresponding issue in the issue tracker.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Added new partner logos to the Home section with direct links to Netlify, Google Cloud, and Holopin websites.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->