Proto files not needed for components in labs? #503
-
I'm sorry I'm not familiar with protobuf so at the risk of asking an incredibly dumb question I noticed the labs don't contain any proto files for content components like text to text Does it mean that proto files are only meant for low level native components? And not for content components? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
No worries. So the two main types of components (explain here: https://google.github.io/mesop/components/#types-of-components) are 1) native components (which are low-level) and use protos and 2) user-defined components, which lab components are an example of, and they don't use protos because these components are entirely written in Python. Content components (see linked page) is an orthogonal concern and is whether the component accepts a child component. Content components can be native or user-defined. |
Beta Was this translation helpful? Give feedback.
No worries. So the two main types of components (explain here: https://google.github.io/mesop/components/#types-of-components) are 1) native components (which are low-level) and use protos and 2) user-defined components, which lab components are an example of, and they don't use protos because these components are entirely written in Python.
Content components (see linked page) is an orthogonal concern and is whether the component accepts a child component. Content components can be native or user-defined.