Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐞 Bug: [Title] Circuit Names Not Preserved Individually Across Tabs, Defaulting to Undefined #408

Open
1 task done
venkateshkasani opened this issue Jan 18, 2025 · 4 comments · May be fixed by #452
Open
1 task done
Assignees
Labels
🐞 bug Something isn't working

Comments

@venkateshkasani
Copy link

Is there an existing issue for this?

  • I have searched the existing issues.

Describe the bug

  1. When a new circuit is created, the respective circuit-tab shows its name defined by the user. But the circuit name inside the properties panel is not updated and it initially remains empty.
  2. Incase of multiple circuit tabs, when a user changes circuit name of any single circuit via the properties panel and switches tab to another circuit, the circuit name inside the properties panel does not update with respective circuit name.

Steps to Reproduce

  1. Go to: https://circuitverse.netlify.app/simulatorvue/
  2. Create a new project and open two different circuit tabs.
  3. Try to change the name of a circuit using the properties panel.
  4. Switch to another circuit tab to see how the same circuit name persists across all the circuit tabs.

Expected Behavior

  1. When user creates a new circuit with a name, the properties panel must reflect the respective circuit name.
  2. Individual circuit changes should not mutate the remaining circuit entity names.

Screenshots

CircuitVerseTwo.-.Google.Chrome.2025-01-19.01-50-19.mp4

Is the faced issue/bug related to the Vue simulator?

Yes

Used Vue simulator with or without backend?

Without Backend

Is the bug present only on the dev server, the build, or both?

Both

Device Information

OS: Windows 10
Browser: Chrome 132.0

Additional Context

No response

Are you working on this issue?

Yes

@venkateshkasani venkateshkasani added pending triage issue yet to be reviewed by maintainers 🐞 bug Something isn't working labels Jan 18, 2025
@venkateshkasani
Copy link
Author

@Arnabdaz Please take a look at this, and could you assign me this issue ?

@tachyons tachyons removed the pending triage issue yet to be reviewed by maintainers label Jan 19, 2025
@Avichal296
Copy link

@venkateshkasani could we collaborate on this issue

@venkateshkasani
Copy link
Author

It is just a bug and almost solved. You can take up another issue. > @venkateshkasani could we collaborate on this issue

@Avichal296
Copy link

ok

@venkateshkasani venkateshkasani linked a pull request Feb 4, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants