-apple-system-headline1
-apple-system-headline2
-apple-system-body
-apple-system-subheadline1
-apple-system-subheadline2
-apple-system-footnote
-apple-system-caption1
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/** | |
* @license | |
* Copyright 2024 Google LLC | |
* SPDX-License-Identifier: Apache-2.0 | |
*/ | |
import { board } from "@google-labs/breadboard"; | |
export default await board(({ text }) => { | |
return { text }; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"edges": [ | |
{ | |
"from": "input-2", | |
"to": "promptTemplate-1", | |
"out": "topic", | |
"in": "topic" | |
}, | |
{ | |
"from": "secrets-5", |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"edges": [ | |
{ | |
"from": "jsonata-5", | |
"to": "output-6", | |
"out": "result", | |
"in": "headlines" | |
}, | |
{ | |
"from": "xmlToJson-4", |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"edges": [ | |
{ | |
"from": "input-1", | |
"to": "prompt-template-6", | |
"out": "text", | |
"in": "topic" | |
}, | |
{ | |
"from": "secrets-8", |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
class Me { | |
constructor() { | |
e1 = new Me; | |
super(); | |
e2 = new Me; | |
} | |
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// dev B: | |
var aBar = document.createElement('a-bar'); | |
aBar.appendChild(someElement); | |
var width = someElement.offsetWidth; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<div id="outerContainer" vertical layout> | |
<slot id="headerContent" name="core-toolbar"></slot> | |
<div id="mainPanel" flex vertical layout> | |
<div id="mainContainer" flex?="{{mode !== 'cover'}}"> | |
<slot id="mainContent" default></slot> | |
</div> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<!-- instance --> | |
<date-range-combo-box> | |
<input type="date" content-slot="start"> | |
<input type="date" content-slot="end"> | |
</date-range-combo-box> | |
<template element="date-combo-box"> | |
<content slot="date"></content> | |
</template> |
The Multiple-actor Problem (MAP) occurs in a web application that contains multiple bits of code, each assuming that they are the only actor in the document. The problem manifests when these assumptions conflict with each other.
Some examples:
- A web app is written in framework A, then later an analytics script B is added. A makes assumptions about lifetime of elements and handling of events. B is not aware of these assumptions and subtly violates them, causing jank (example)
- A web app is written using framework A. Attempting to introduce a widgets built using framework B results in weird errors, because B is violating A's assumptions about control of document state (examples 1, [2](http://stackoverflow.com/questions/254
NewerOlder