Closed switschel closed 3 weeks ago
Currently if a mapping could not be activated for some connectors the user does not receive any feedback.
Suggested Improvement: When activating a mapping the message "Could not be activated for connector x".
Reason for this could be because a connector is not supporting some specific mappings e.g. wildcard mappings.
Other Improvement: Check during mapping creation that this will not be working for connector x.
Concrete Example: MQTT Service + Mapping created for "events/#" etc. Mapping could be activated but no feedback given to the user afterwards.
The first improvements were in included in:
This enhancement was included in 198a9c25f6a6cba5bfa9c54ccbe455f47672868a
Currently if a mapping could not be activated for some connectors the user does not receive any feedback.
Suggested Improvement: When activating a mapping the message "Could not be activated for connector x".
Reason for this could be because a connector is not supporting some specific mappings e.g. wildcard mappings.
Other Improvement: Check during mapping creation that this will not be working for connector x.
Concrete Example: MQTT Service + Mapping created for "events/#" etc. Mapping could be activated but no feedback given to the user afterwards.