Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

You can see from the original issue `config.value.value` was causing the multiple `initStore` INTISTORE,OLDVAL=>

Open
  • Is something wrong?
#321 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
frontend

Research direction

Start by reproducing the watch(config, ...) example from the issue in the element-plus-playground and inspect the onTrigger output for repeated initStore calls. Compare the behavior of config with the reported config.value.value case; done means the reproduction no longer causes unintended multiple initialization calls.

Written by the indexing model from the issue text.

Description

You can see from the original issue config.value.value was causing the multiple initStore.
ts
watch(
config,
(newVal, oldVal) => {
if (isEqual(newVal, oldVal)) return console.log('cancel')
initStore()
},
{
immediate: true,
onTrigger(event) {
console.log(event.key)
}
}
)

Dominant language
Vue
Stars
227
Forks
80
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 element-plus/element-plus-playground

All issues in element-plus/element-plus-playground

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.