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.

Sign up for GitHub

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

Jump to bottom

Bug: getting duplicate name #1921

Closed
dqnykamp opened this issue Feb 6, 2023 · 0 comments · Fixed by #1929
Closed

Bug: getting duplicate name #1921

dqnykamp opened this issue Feb 6, 2023 · 0 comments · Fixed by #1929
Assignees
@dqnykamp
Labels
bug Something isn't working DoenetML core

Comments

@dqnykamp
Copy link
Member

dqnykamp commented Feb 6, 2023

This DoenetML leads to a "Duplicate component name" error.

<triggerSet>
  <updateValue target="v2.head.coords" />
  <updateValue target="v3.head.coords" />
</triggerSet>


<updateValue  />
<updateValue target="v3.head.coords" />
@dqnykamp dqnykamp added bug Something isn't working DoenetML core labels Feb 6, 2023
@dqnykamp dqnykamp changed the title Bug: getting duplicated name Bug: getting duplicate name Feb 6, 2023
@dqnykamp dqnykamp mentioned this issue Feb 11, 2023
Merged
@dqnykamp dqnykamp self-assigned this Feb 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dqnykamp dqnykamp

Labels
bug Something isn't working DoenetML core
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix duplicate name in updateValue bug dqnykamp/DoenetTools
1 participant
@dqnykamp