Skip to content

Event data port prototype bindings created by graphical editor are not serialized correctly #2834

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

Closed
philip-alldredge opened this issue Aug 19, 2022 · 0 comments · Fixed by #2830
Assignees
Milestone

Comments

@philip-alldredge
Copy link
Collaborator

Summary
Event data port prototype bindings created by grpahical editor are not serialized correctly. When creating an event data port prototype binding as done in the PrototypeEndToEndTest, the test fails because the binding is serialized as eventData port. Note that in the current master branch, the test fails before it gets to that point due to the dialog labeling changes. Once #2833 is merged, the test fails due to the serialization issue.

Expected behavior
Event data port feature prototype bindings created with the graphical editor should serialize as event data port.

Actual behavior
Event data port feature prototype bindings created with the graphical editor serialize as eventData port.

Steps To Reproduce
Run the PrototypeEndToEndTest or create a event data port prototype binding with the graphical editor.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

@lwrage lwrage changed the title Event data port prototype bindings created by grpahical editor are not serialized correctly Event data port prototype bindings created by graphical editor are not serialized correctly Aug 25, 2022
@lwrage lwrage added this to the 2.12.0 milestone Aug 25, 2022
@lwrage lwrage self-assigned this Aug 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants