You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Describe the message type using unique naming to not conflate other aspects of the zilla config like a binding's type.
Describe the solution you'd like
Use the word model when referring to the message type as it is stored and transmitted. Use the word view when describing a the message type after the stored message is converted from or to.
Is your feature request related to a problem? Please describe.
Describe the message type using unique naming to not conflate other aspects of the zilla config like a binding's
type
.Describe the solution you'd like
Use the word
model
when referring to the message type as it is stored and transmitted. Use the wordview
when describing a the message type after the stored message is converted from or to.generic example
Additional context
Specific examples from the bindings this change may affect.
Kafka:
HTTP:
MQTT
Tasks
types-*
modules tomodel-*
modulesValidatorFactorySpi
andConverterFactorySpi
toModelFactorySpi
Validator
andConverter
toModel
ValidatorContext
andConverterContext
toModelContext
ValidatorHandler
andConverterHandler
obtained fromModelContext
ValidatorConfig
andConverterConfig
intoModelConfig
, restrictview
via schema?http
andmqtt
reference docs to allow onlyvalidators
(notconverters
) in type information (usingmodel
view
terms now instead)protobuf
support in zilla reference (usingmodel
view
terms)The text was updated successfully, but these errors were encountered: