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

BSON Serialization Exceptions for non-Str and non-Int type dict keys #30

Open
OluAgunloye opened this issue Sep 23, 2020 · 1 comment
Open

BSON Serialization Exceptions for non-Str and non-Int type dict keys #30

OluAgunloye opened this issue Sep 23, 2020 · 1 comment

Comments

@OluAgunloye
Copy link

In workflows that allow the SelectNextStep key (the Decide step type below for example):
image

Issue:
One can see that BSON has an issue with the key names that aren't str or int types.
image
@OluAgunloye OluAgunloye changed the title BSON Serialization Exceptions in mixed type dict keys BSON Serialization Exceptions for non-Str and non-Int type dict keys Sep 23, 2020
@OluAgunloye
Copy link
Author

OluAgunloye commented Sep 23, 2020 •
edited
Loading

Comment: The issue is is referenced exactly in
https://stackoverflow.com/questions/50610433/error-handle-element-name-is-not-valid

Just avoid the use of decimals/periods in your key/property names in the SelectNextStep field.

EDIT: This isn't a true fix so I'm keeping the issue open, but it is a work around.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@OluAgunloye