reactjs / reactjs/react.dev

Object oriented programming Over functional programming?

Open
#3,982 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
11.8k
Forks
7.9k
Avg merge
1d 11h
Merged PRs (30d)
11

Description

I am Working on Admin Panel which has 30-40 Master table which contains CRUD functionality.
There are few masters which I need to call again and again in different masters. Eg we need to call country master in State & City inorder to add State and City because they both should in particular country. So the problem is I have to write or copy paste entire getCountry() Code in State & again in City. In OOPs we used to just create function at once then call it anywhere with single line of code.

But react that's not working as expected. So what's the best way to do that? Hope I am clear here.

Points / My concern

  1. There are lot of repetition for calling APIs.
  2. In oops we create function and just call that using single like and use it. But not in react we have to write setState logic and need to handle success, error logic everywhere again and again

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no file, test, or entry point; start by clarifying whether a React documentation page is requested and which reusable API-fetching pattern should be covered. Done would require an agreed scope and documentation change addressing the stated repetition and success/error handling concerns.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.