Back to Examples
- Binding patterns
- Typed binding pattern
- Wildcard binding pattern
- List binding patterns
- Rest binding pattern in list binding pattern
- Mapping binding pattern
- Rest binding pattern in mapping binding pattern
- Error binding pattern
- Rest binding pattern in error binding pattern
- Single use of typed binding patterns
- Single use of typed binding patterns with on fail clause
- Iterative use of typed binding patterns
- List binding pattern in match statement
- Mapping binding pattern in match statement
- Error binding pattern in match statement
- Query expressions
- Sort iterable objects
- Let clause
- Limit clause
- Join iterable objects
- Outer Join clause
- Query tables
- Create tables with a query
- Create maps with a query
- Create streams with a query
- On conflict clause
- Advanced conflict handling
- Iterate over XML with a query
- Nested query expressions
- Destructure records using a query
- Querying streams
- Aggregation
- JSON type
- Access JSON elements
- Access optional JSON elements
- Match statement with maps
- Convert from user-defined type to JSON
- Convert from table and XML to JSON
- Convert from JSON to user-defined type
- Cast JSON to user-defined type
- Resource method typing
- JSON numbers
- JSON to record
- JSON to record with projection
- JSONPath expressions
- Asynchronous function calls
- Named workers
- Sequence diagrams
- Wait for workers
- Strands
- Named worker return values
- Alternate wait
- Multiple wait
- Named workers and futures
- Inter-worker message passing
- Alternate receive
- Multiple receive
- Conditional send
- Inter-worker failure propagation
- Named worker with on fail clause
- Synchronize message passing
- Asynchronize message passing
- Flush
- Fork
Mapping binding pattern
A mapping binding pattern matches a mapping value with its fields. A record
type will be assigned to the mapping binding pattern if it successfully matches the value. Both the map
and record
types can be used in mapping binding patterns. Record destructuring in binding patterns can be used to refer to existing variables as a record, destructure the given value on the right-hand side, and assign the values to each individual variable of the record during the runtime. These binding patterns are especially helpful when dealing with queries and are useful when destructuring JSON values.
import ballerina/io;
type Person record {|
int id;
string fname;
string lname;
|};
public function main() {
// `_` is used to ignore the value of the `id` field.
// The values of the `fname` and `lname` fields are bound to the `firstName` and
// `lastName` variable names.
Person {id: _, fname: firstName, lname: lastName} = getPerson();
io:println(firstName + " " + lastName);
// The `fname` and `lname` fields do not have explicitly defined variable names.
// `{fname, lname}` is the same as `{fname: fname, lname: lname}`.
// The `id` field is ignored as it is not bound to a variable.
Person {fname, lname} = getPerson();
io:println(fname + " " + lname);
string givenName;
string surname;
// This destructures and assigns the values of the fields in the destructed record
// to the variable references.
// The values of the `fname` and `lname` fields are assigned to the `givenName` and
// `surname` variables.
{fname: givenName, lname: surname} = getPerson();
io:println(givenName + " " + surname);
}
function getPerson() returns Person {
Person person = {id: 1001, fname: "Anne", lname: "Frank"};
return person;
}
$ bal run mapping_binding_pattern.balAnne FrankAnne FrankAnne Frank
Related links
PreviousRest binding pattern in list binding pattern
NextRest binding pattern in mapping binding pattern