Notifications ​

console_log ​

Output a message to the browser console.

console_log(
  batch:   String,  # [null]  - add the operation to a named batch
  cancel:  Boolean, # [false] - cancel the operation (for use on client)
  delay:   Integer, # [0]     - wait for n milliseconds before running
  level:   String,  # ["log"] - optionally specify one of "warn", "info" or "error"
  message: String,  # [""]    - required, although it can be empty
)

Life-cycle Callback Events ​

• cable-ready:before-console-log
• cable-ready:after-console-log

Life-cycle events for console_log are raised on document.

Reference ​

• https://developer.mozilla.org/en-US/docs/Web/API/Console/log

console_table ​

Output a table to the browser console.

console_table(
  batch:   String,          # [null]  - add the operation to a named batch
  cancel:  Boolean,         # [false] - cancel the operation (for use on client)
  columns: Array,           # [[]]    - optional array of strings
  delay:   Integer,         # [0]     - wait for n milliseconds before running
  data:    Object or Array, # [{}]    - required, although it can be empty
)

The Console Inspector will build a simple table of values when provided with relatively normalized data in Array or Object format via the data option. You can further specify an array of Strings to create an "allowlist" of columns to display (and hide the rest).

Life-cycle Callback Events ​

• cable-ready:before-console-table
• cable-ready:after-console-table

Life-cycle events for console_table are raised on document.

Reference ​

• https://developer.mozilla.org/en-US/docs/Web/API/Console/table

notification ​

Display a native system notification to the end user. This will happen outside the top-level browsing context viewport, so therefore can be displayed even when the user has switched tabs or moved to a different app. Native notifications are designed to be compatible with existing notification systems, across different platforms.

You can learn about all of the possible options on MDN.

The most obviously useful is body which is the message below the title. You might also want to specify icon which takes a URL to an image. You can even vibrate their phone or mark your message as silent.

notification(
  batch:   String,  # [null]   - add the operation to a named batch
  cancel:  Boolean, # [false]  - cancel the operation (for use on client)
  delay:   Integer, # [0]      - wait for n milliseconds before running
  title:   String,  # required, although it can be empty
  options: Object   # see options such as body, icon, vibrate, silent
)

Life-cycle Callback Events ​

• cable-ready:before-notification
• cable-ready:after-notification

Life-cycle events for notification are raised on document.

Reference ​

• https://developer.mozilla.org/en-US/docs/Web/API/Notifications_API

Example: ​

notification(
  title: "You are the best.",
  options: {
    body: "How does it feel to be your parents' favourite?",
    icon: "https://source.unsplash.com/256x256",
    vibrate: [200, 200, 200],
    silent: false
  }
)

Click Handlers ​

For reasons unclear, the Notification API doesn't make it easy to attach a click handler to your notifications. It could just be that they cannot guarantee it will work across all devices. If you have determined that you need to define a click handler, the recommended solution is to use a dispatch_event operation to send an event to the client. Your event handler can then build up a Notification instance molded to your specific tastes.

document.addEventListener('my-app:notify', e => {
  let permission
  Notification.requestPermission().then(result => {
    permission = result
    const { title, options, clickUrl } = e.detail
    if (result === 'granted') {
      const notification = new Notification
      notification.onclick = () => window.open(clickUrl)
      notification(title || '', options)
    }
  })
})

play_sound ​

Play an .mp3 or .ogg audio file in the browser.

The sound starts playing when the minimum viable amount of the sound file has been downloaded. If another sound request comes in while the first one is still playing, the first one stops.

CableReady subtly captures the first user interaction on the page to ensure this operation works well on all browsers, including Safari Mobile. A silent mp3 is played as soon as the page context is established. It is base64 encoded so there is no network request. At 93 bytes, it is the minimum viable mp3!

play_sound(
  batch:  String,  # [null]   - add the operation to a named batch
  cancel: Boolean, # [false]  - cancel the operation (for use on client)
  delay:  Integer, # [0]      - wait for n milliseconds before running
  src:    String   # required - URL for audio file
)

Life-cycle Callback Events ​

• cable-ready:before-play-sound
• cable-ready:after-play-sound

Life-cycle events for play_sound are raised on document.

cable-ready:after-play-sound is emitted either after the sound has finished playing, or immediately if the operation is cancelled.

Importing AudioOperations ​

After adding play_sound to the library, people came out of the woodwork to say that our clever implementation was messing up their audio player, or not working well with IE11. We experimented with several workarounds to opt-in and opt-out, but ultimately decided that this provided the perfect opportunity to build out our vision for a general purpose packaged operation API. We think it turned out great!

Find a step-by-step example on how to import AudioOperations here.

Reference ​

• https://developer.mozilla.org/en-US/docs/Web/API/HTMLAudioElement/Audio
• https://developer.mozilla.org/en-US/docs/Web/HTML/Element/audio