Issue:

• when a route like /doesnotexist is accessed directly, the editor preview simply stays blank
• when some routes are defined in a top-block, and more routes are defined in sub-blocks, changing the sub-block leads to no visual change

Proposed solution:

• when nothing gets displayed, the available route-tree in the currently edited block should be displayed as a 404 message

if a text input component is used inside of another interpreter, it gets re-constructed on each change

build components with http://reactdesktop.js.org/demo/ in a seperate interpreter-retriever to show flexibility

• create a React-component from an accordeon from here: https://www.w3schools.com/howto/howto_js_accordion.asp
• group interpreters in designer by their url (e.g.: shnyder/md/NavBarWActions)
• adjust dropzone and lower tool-buttons

RefMap-Handling will be split into two parts: prefill and fill

• implement and test reducer for prefill

• implement and test interpreter-matcher changes for prefill

• implement and test reducer for fill

• implement and test interpreter-matcher changes for fill

• create a form that's able to save a row in a spreadsheet application

Basic type safety scaffolding has been set up in src/ldaccess/ldtypesystem.

• Deny linking in Designer for ports with non-matching types

• Highlight (in-)ports that work when dragging a (out-)port (and vice versa)

when serializing from the designer, choose and implement a way to delete previous interpreters

State-generatorFns should be able to take a canInterpretType as a single Kv

When there's a BlueprintConfig declaring that it canInterpretType (e.g. schema.org/ImageObject), and it has some interpretableKeys that exist on that type (e.g. schema.org/contentUrl or schema.org/name), and it doesn't fill those keys but instead has a possible singleKV with that type, then the generatorFunctions

• getDerivedItptStateFromProps
• getDerivedKVStateFromProps
• initLDLocalState

should take the values from that singleKv instead and distribute it among ldTypes, localValues and compInfos. Determining the singleKv should be done with determineSingleKVKey

All components should use the React 16.X flow without deprecated functions

game/

• PureFourFieldsView
• PureSingleFieldView

generic/

• PureBaseContainerRewrite
• PureRefMapItpt

md/content/

• PureBaseDataTypeInput
• PureSingleImageSelector

md/interaction/

• PureMDButton

md/navigation/

• PureBottomNavigation
• PureNavBarWActions
• PureNavProcessAtom
• PureNavSearchBar

peripherals/camera/

• EANScanner

routing/

• PureRouteComponent

visualcomposition/

• PureImgDisplay
• PureImgHeadSubDesc

write tests that make sure that updates are propagated recursively on state changes

create a node in the designer from an API access point, either by dragging and dropping a typescript file and getting information about functions and types from it, or by hooking into a swagger-generator

components like bottom navigation and EAN scanner export values. It should be possible to set them as dynamic output of a RefMap-BlueprintConfig containing that component

Problem: The component which triggers LDOPTIONS_KV_UPDATE does not get an update for its own triggering value in the store.

• fix error, where ripple-effect from react-toolbox doesn't "grow" (only shows maximum size)
• fix huge filesize of js-file (containing css) by separating/trimmming CSS modules, SCSS etc. (file size is displayed after running "yarn build"