Bixby Developer Center

Guides
References

layout-match

optionalvalue required

Defines a group view using an existing layout that matches on the specified value. It will lookup the layout for a given concept in a given mode.

Note

Be aware of which components you are adding to your layouts and layout macros, because different components are available under different views. If you call a layout or layout macro in a view and that layout specifies a component that the view does not support, Bixby Developer Studio will throw an error. Similarly, you should consider which layout macros are being called within a layout itself. The same layout macro invoked in one component might not be valid if used within a different component, as the list of supported child components could differ.

You can read the Designing with Bixby Views design guide and the Building Bixby Views (UI) developer guide to check if your layout is using the correct components for that moment and that view.

Example

      layout-match (hotel) {
mode (Details)
}

View a39ed2b7264905c75f00b50a7eb0215f2cd00796 on GitHub

        detail-view {
render {
layout-match (this) {
mode (Details)
}
}
}

View f594fd2133094c3cca77065ab802c8a7b5c0a308 on GitHub

You can repeat components within a layout-match content container using a for-each loop:

layout-match {
mode (...)
match: ...
content {
for-each (x) {
as (y) {
section {
content {
...
}
}
}
}
}

Child Keys

select-button-text
required
Selection button text
mode
optional
Defines the layout type and/or which layout file to call