Refactor IconComponent as a Shared component

[palisadoes]

Is your feature request related to a problem? Please describe.

This component is imported by components in the src/shared-components folder. This means it is a shared component.

src/components/IconComponent/IconComponent

Describe the solution you'd like

1. Migrate the component to the src/shared-components folder. Update all imports that referred to the component in its previous location to the new location.
2. Make sure the locations of files for the component complies with our reusable component policy.
   • https://docs-admin.talawa.io/docs/developer-resources/reusable-components
   1. For example types need to be located in a sub folder of this directory

      src/types/shared-components/
      

3. All other functionality must be maintained
4. All tests must be valid and achieve 100% test code coverage

Describe alternatives you've considered

• See above

Approach to be followed (optional)

• N/A

Additional context

• N/A

[saadzaveri26]

Hi @palisadoes I would like to take this up.

My Approach:

Locate & Extract: I will identify the current IconComponent (likely nested within a specific feature folder) and migrate it to src/shared-components/IconComponent to align with the reusable component policy.

Refactor: I will ensure it accepts dynamic props (className, size, color) to be truly generic.

Update References: I will scan the codebase and update all import paths to point to the new shared location.

Testing: I will verify that existing unit tests pass and add a snapshot test for the new shared component if needed.

I am ready to start immediately. Please assign this to me.

[NishantSinghhhhh]

@palisadoes can I work on this issue ??

[palisadoes]

Hi @palisadoes I would like to take this up.

My Approach:

Locate & Extract: I will identify the current IconComponent (likely nested within a specific feature folder) and migrate it to src/shared-components/IconComponent to align with the reusable component policy.

Refactor: I will ensure it accepts dynamic props (className, size, color) to be truly generic.

Update References: I will scan the codebase and update all import paths to point to the new shared location.

Testing: I will verify that existing unit tests pass and add a snapshot test for the new shared component if needed.

I am ready to start immediately. Please assign this to me.

@saadzaveri26

We will only be assigning issues or merging PRs for persons who have:

1. At least 18 months of verifiable GitHub history
2. Consistent code updates throughout their GitHub life, especially the most recent 12 months.

You can find more details on the rationale here: https://developer.palisadoes.org/docs/contributor-guide/issues#manual-assignments

If you have merged PRs in other open source projects, let us know and post links to them. We will consider those contributions in our evaluation. If you have other relevant, verifiable and sufficient experience let us know too.

[palisadoes]

@NishantSinghhhhh

As someone who has merged code into this repository you may now use the issue auto-assignment feature outlined here: ISSUE_GUIDELINES.md

[Priyanshubhartistm]

/assign