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

Serialized SwitchNode looses "order and "direction" properties #340

Closed
MarinPinchinatLoth opened this issue Jan 20, 2022 · 0 comments · Fixed by #346
Closed

Serialized SwitchNode looses "order and "direction" properties #340

MarinPinchinatLoth opened this issue Jan 20, 2022 · 0 comments · Fixed by #346

Comments

@MarinPinchinatLoth
Copy link
Contributor

  • Do you want to request a feature or report a bug?
    A bug

  • What is the current behavior?
    When serialized to Json, SwitchNodes are loosing their 'order" and "direction" properties.

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

  1. Create a SwitchNode with an order and a direction.
  2. Serialize it using "writeJsonContent" method
  3. Deserialize it.

Order and direction are now null values.

  • What is the expected behavior?
    Order and direction values should remain the same as before serialization.

  • What is the motivation / use case ?
    We need to serialize graphs in order to store them into a database

  • Please tell us about your environment:

    • PowSyBl Version: 2.6.0
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, spectrum, etc)

Workaround : we created a CustomSwitchNode class extending SwitchNode, overriding writeJsonContent method.

@MarinPinchinatLoth MarinPinchinatLoth changed the title Serilized SwitchNode looses "order and "direction" properties Serialized SwitchNode looses "order and "direction" properties Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant