Uh oh! We couldn’t find any match.

Please try other search keywords.

Bixby Developer Center

Guides

result-view

optional

Defines the layout used for results returned from Bixby.

result-view {
match: Hotel (this)

render {
if (size (this) == 1) {
layout-match (this) {
mode (Details)
}
} else {
list-of (this) {
has-details (true)

highlights {
select (pick) {
label ("Based on your preferences")
order-by {
sorting {
by-preferences
}
}
layout-macro (hotel_highlight) {
param (hotel) {
expression (pick)
}
}
}
}
where-each-page (page) {
where-each-item (item) {
layout-match (item) {
mode (Summary)
}
}
}
}
}
}
}

Within result-view, you can determine what to render based on the number of results returned, which might be zero, one, or more. For more information, see Result Views in Bixby Views.

A result-view can be rendered by a halt effect if the view's match pattern matches the halted node. In this case, the view will always have zero results.

Child Keys

match
required
Match patterns are used to dynamically look up the appropriate data (e.g., layout, dialog, selection strategies, views) for the current context
app-launch
optional
When triggered by this result-view, exits users from Bixby and opens a client application
app-punch-out[deprecated]
optional
This key is deprecated
conversation-drivers
optional
Provide convenient shortcuts to related actions in the form of buttons that appear at the bottom of the screen
followup
optional
Defines a followup, which gives users an opportunity to do a specific follow-up action by responding to a yes or no question
message
optional
Message to display to users
refresh
optional
Allows for the results to be periodically refreshed, as long as the UI remains open
render
optional
Renders the specified view for users