Add regression coverage for the deprecated static mock flag in config

Open Beginner friendly
#4,010 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
92/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
frontend, testing

Research direction

Start with web/src/config.ts to confirm the exported USE_MOCK value, then open web/src/config.test.ts and run that targeted Vitest file. Add the focused assertion described in the issue; done means the test verifies USE_MOCK === false and the targeted test passes.

Written by the indexing model from the issue text.

Description

Problem

web/src/config.ts exports USE_MOCK for backward compatibility, but the existing test only covers API_BASE_URL. The deprecated flag is not protected by a regression test, so it could be accidentally flipped and reintroduce the legacy mock-data code path.

Expected behavior

  • USE_MOCK remains alse for the current Studio runtime.
  • A focused Vitest case fails if the flag is changed.

Scope

Only add regression coverage for web/src/config.test.ts. No runtime code changes.

Acceptance criteria

  • A Vitest assertion verifies USE_MOCK === false.
  • The targeted test file passes.
Dominant language
Java
Stars
1.4k
Forks
692
Avg merge
2d 18h
Merged PRs (30d)
69

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.

More from apache/rocketmq-dashboard

All issues in apache/rocketmq-dashboard

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.