Skip to content

Add Typescript Type Checking & Eslint linting to the /src directory #69

Description

@palisadoes

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

  1. The home page of the developer.palisadoes.org website is located in the src/ directory
  2. We need the typescript code in this directory to match the quality of talawa-admin

Describe the solution you'd like

With GitHub Actions:

  1. Add your changes to the .github/workflows/pull-request.yml file
  2. Add the checks and linting to a pre-commit husky workflow

Other

  1. Add type checking to the directory/directories3. Add linting to the directories using the eslint appropriate configuration sections from talawa-admin4. The docs/ directory contains the Docusaurus files for the website. Ensure that the Docusaurus site functions by testing it on your local machine.
  2. Make appropriate changes to .gitignore files

Describe alternatives you've considered

  • N/A

Approach to be followed (optional)

  • N/A

Additional context

  • N/A

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

Activity

  1. avinxshKD commented on Oct 14, 2025

    @avinxshKD

    would like to work on this, can you pls assign this to me..

  2. added a commit that references this issue on Oct 14, 2025
    1c1fe4a
  3. palisadoes commented on Oct 17, 2025

    @palisadoes
    ContributorAuthor

    would like to work on this, can you pls assign this to me..

    @avinxshKD

    Unfortunately, because of recent abuse, we will only be assigning issues to persons who have:

    1. At least a year of GitHub history
    2. Active code updates throughout their GitHub life

    This is a new policy triggered by newly created accounts that:

    1. Use automation to blindly submit and update pull requests, ignoring reviewers.
    2. SPAM our volunteers to be assigned issues to the exclusion of others.
    3. Frequently abandon issues after being assigned.
    4. Frequent closing of pull requests

    As expected, we need contributors who are interested in coding with a proven track record. This is an unfortunate development but the recent abuse of the system has given us no choice.

    Unassigning

  4. github-actions commented on Oct 25, 2025

    @github-actions

    This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

  5. pavanydg commented on Nov 5, 2025

    @pavanydg

    Hi @palisadoes, i would like to work on this. Can i take this up?

  6. github-actions commented on Nov 14, 2025

    @github-actions

    This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

  7. palisadoes commented on Nov 14, 2025

    @palisadoes
    ContributorAuthor

    Unassigned. Inactivity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions