qiuyanjun888 opened a new pull request, #28440:
URL: https://github.com/apache/flink/pull/28440

   ## What is the purpose of the change
   
   This pull request fixes FLINK-39587 by making the web dashboard lint script 
run ESLint without the persistent cache. This prevents CI lint from tolerating 
stale prettier/template drift that can be hidden by `.eslintcache`.
   
   Jira: https://issues.apache.org/jira/browse/FLINK-39587
   
   ## Brief change log
   
   - Removed `--cache` from the web dashboard `lint` script.
   - Removed `--cache` from `lint:fix` so the prescribed auto-fix path also 
checks/fixes all source files.
   - Ran `npm run lint:fix`, which produced one scoped stylelint property-order 
fix in `job-exceptions.component.less`.
   
   ## Verifying this change
   
   This change is already covered by the web dashboard lint/build checks and 
can be verified as follows:
   
   - `node <script check> package.json lint/lint:fix contain no eslint --cache` 
(failed before the change, passed after)
   - `npm run lint:fix`
   - `rm -f .eslintcache && npm run lint`
   - `npm run build`
   - `git diff --check`
   
   ## Does this pull request potentially affect one of the following parts:
   
   - Dependencies (does it add or upgrade a dependency): no
   - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
   - The serializers: no
   - The runtime per-record code paths (performance sensitive): no
   - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
   - The S3 file system connector: no
   
   ## Documentation
   
   - Does this pull request introduce a new feature? no
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (please specify the tool below)
   
   Generated-by: Hermes Agent (OpenAI GPT-5.5)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to