langgenius/dify

[Chore/Refactor] Mark the props of the component as read-only

Open

#25219 opened on Sep 5, 2025

View on GitHub
 (6 comments) (2 reactions) (2 assignees)TypeScript (141,412 stars) (22,210 forks)batch import
good first issuerefactor🙏 help wanted

Description

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for refactoring, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Description

Mark the props of the component as read-only

Motivation

https://eslint-react.xyz/docs/rules/prefer-read-only-props

Additional Context

No response

Contributor guide

Tech stack
typescriptreact
Domain
frontend
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
TypeScriptReact
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
The issue asks to mark all React component props as read only following the eslint react rule 'prefer read only props'. First, review the rule documentation at https://eslint react.xyz/docs/rules/prefer read only props. Then, search the codebase for React components where props are not marked as readonly. Add the 'readonly' modifier to prop definitions in TypeScript. The changes are mechanical but may involve many files. Existing comments or PRs (none linked) may provide context.