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
Instead there should be a dedicated repeated message to describe these templates such as:
messageTemplate {
optionalstringname=1;
optionaluint32ordinal=2; // sort number - just in case if the list order can't be preserved, but shouldoptionalstringbody=3; // or bytes - then we should provide charset coding, however!optionalstringlayout=4; // or bytes - then we should provide charset coding, however!optionalstringstyle_url=5; // Why is style (css) just a URL while the others payload data?
}
Furthermore, the response is no more than an Any with id while in case of an error the keyword error shares the same layer as the render results! Errors and render results should be separated, rather use Status and/or OperationStatus like all the other services.
messagePayload {
// json with <key, template> pairs// e.g. { 'subject': ..., 'message':....}optionalgoogle.protobuf.Anytemplates=1;
optionalgoogle.protobuf.Anydata=2; // data to fill template withoptionalstringstyle_url=3; // stylesheet URLenumStrategy { // style-applying 'strategy'INLINE=0;
COPY=1;
}
optionalStrategystrategy=4; // inlining, copying CSS into <style>, etc...// rendering options JSON objectoptionalgoogle.protobuf.Anyoptions=5;
// content type for rendering such as 'application/html' or 'application/text'optionalstringcontent_type=6;
}
messageRenderResponse {
optionalstringid=1;
repeatedgoogle.protobuf.Anyresponses=2; // error or HTML contents
}
The text was updated successfully, but these errors were encountered:
The rendering message type is very much under-defined.
It declares
Any
where a certain known structure is requested such as fortemplates
i.e.:Instead there should be a dedicated repeated message to describe these templates such as:
Furthermore, the response is no more than an
Any
withid
while in case of an error the keyworderror
shares the same layer as the render results! Errors and render results should be separated, rather useStatus
and/orOperationStatus
like all the other services.packages/protos/io/restorecommerce/rendering.proto
The text was updated successfully, but these errors were encountered: