Documentation
develop
develop
  • Cubbles documentation
  • First steps
    • Generate a project
    • Create a webpackage
    • Create an elementary component
    • Create a compound component
      • Compound slot initialization
  • Runtime extension - RTE
    • User guide
      • RTE Integration
      • The Cubbles TAG API
        • The Cubbles Dependency API
      • The Cubbles Javascript API
        • Interacting with Cubbles from the outside
        • Adding dynamic connections
        • Interacting with Elementary Cubbles from the inside
      • The RTE Processing
        • RTE initialization and rendering timeline
      • The Cubbles IFrame API
        • The Cubbles IFrame Resizer API
      • The Cubbles mutation based start event API
      • FAQs
        • How to manually resolve dependency conflicts?
        • How to create a component instance dynamically?
        • How to render HTML Markup coming from input slot?
        • How to replace a dependency when declaring a component instance?
        • How to synchronize multiple dataflows between component instances?
        • How to handle the copyValue flag for non serializable instances?
    • Contributor guide
      • CIF processing
  • Developing with the vanilla boilerplate
    • Creating a new project
    • Developing elementaries using the vanilla boilerplate
    • Developing compounds using the vanilla boilerplate
    • Using the vanilla boilerplate scripts
  • Coder devtools - CDT
    • User guide
      • Create Cubbles artifacts
      • Upload a Webpackage
      • Generate a README file
      • Rename an artifact
      • Configure network proxy
      • Validate the manifest.webpackage file
      • Change active webpackage
      • Bulk upload of webpackages
      • Release a webpackage
      • Update the RTE version of a webpackage
      • Prepare a webpackage to be released
      • Update webpackage to the next development version
      • Generate a test environment for a component
      • Testing Cubbles components
      • Validate sources
      • Create a demo webpackage
    • Contributor guide
      • Checklist for releasing a new webpackage.modelVersion
  • Terms and concepts
    • Webpackage
    • Artifacts
    • User roles
    • Base
Powered by GitBook
On this page
  1. Runtime extension - RTE
  2. User guide
  3. FAQs

How to handle the copyValue flag for non serializable instances?

By default, a slot value is copied when it is propagated due to a connection. However, that is behaviour is problematic when a slot value is non serializable (e.g. an object with circular references) since it cannot be copied. To be able to have non serializable slot values, you may set the copyValue property of a connection to false. In that case, a slot value will not be copied, instead, it will be passed as a reference.

This way, a connection definition between a componentA and a componentB may look as follows:

...
{
    "connectionId": "nonSerializableConnection",
    "source": {
        "memberIdRef": "componentA",
        "slot": "nonSerializableSlot"
    },
    "destination": {
        "memberIdRef": "componentB",
        "slot": "nonSerializableSlot"
    },
    "copyValue": false
}
...
PreviousHow to synchronize multiple dataflows between component instances?NextContributor guide

Last updated 6 years ago