chromex.ext.idltest — binaryage/chromex 0.9.1

clj

An API to test IDL schema specifications.

• available since Chrome master
• https://developer.chrome.com/extensions/idltest

api-table clj

gen-call clj

gen-wrap clj/s macro

(gen-wrap kind item-id config & args)

get-array-buffer clj/s macro

(get-array-buffer)

This function returns a core.async channel of type promise-chan which eventually receives a result value. Signature of the result value put on the channel is [buffer] where:

|buffer| - https://developer.chrome.com/extensions/idltest#property-cb-buffer.

In case of an error the channel closes without receiving any value and relevant error object can be obtained via chromex.error/get-last-error.

https://developer.chrome.com/extensions/idltest#method-getArrayBuffer.

get-array-buffer* cljs

(get-array-buffer* config)

nocompile-func clj/s macro

(nocompile-func switch)

This function should not have C++ code autogenerated (the variable name |switch| should cause compile errors if it does). But the name should get defined and made visible from within extensions/apps code.

|switch| - https://developer.chrome.com/extensions/idltest#property-nocompileFunc-switch.

https://developer.chrome.com/extensions/idltest#method-nocompileFunc.

nocompile-func* cljs

(nocompile-func* config switch)

nodefine-func clj/s macro

(nodefine-func switch)

This function should not have C++ code autogenerated (the variable name |switch| should cause compile errors if it does). The name should also never be defined in Javascript and invisible to extensions/apps code.

|switch| - https://developer.chrome.com/extensions/idltest#property-nodefineFunc-switch.

https://developer.chrome.com/extensions/idltest#method-nodefineFunc.

nodefine-func* cljs

(nodefine-func* config switch)

send-array-buffer clj/s macro

(send-array-buffer input)

Functions for testing binary data request/response parameters. The first two just return back the bytes they were passed in an array.

|input| - https://developer.chrome.com/extensions/idltest#property-sendArrayBuffer-input.

This function returns a core.async channel of type promise-chan which eventually receives a result value. Signature of the result value put on the channel is [array] where:

|array| - https://developer.chrome.com/extensions/idltest#property-cb-array.

In case of an error the channel closes without receiving any value and relevant error object can be obtained via chromex.error/get-last-error.

https://developer.chrome.com/extensions/idltest#method-sendArrayBuffer.

send-array-buffer* cljs

(send-array-buffer* config input)

send-array-buffer-view clj/s macro

(send-array-buffer-view input)

TODO(asargent) - we currently can't have [instanceOf=ArrayBufferView], I think because ArrayBufferView isn't an instantiable type. The best we might be able to do is have a 'choices' list including all the typed array subclasses like Uint8Array, Uint16Array, Float32Array, etc.

|input| - https://developer.chrome.com/extensions/idltest#property-sendArrayBufferView-input.

This function returns a core.async channel of type promise-chan which eventually receives a result value. Signature of the result value put on the channel is [array] where:

|array| - https://developer.chrome.com/extensions/idltest#property-cb-array.

In case of an error the channel closes without receiving any value and relevant error object can be obtained via chromex.error/get-last-error.

https://developer.chrome.com/extensions/idltest#method-sendArrayBufferView.

send-array-buffer-view* cljs

(send-array-buffer-view* config input)

tap-all-events clj/s macro

(tap-all-events chan)

Taps all valid non-deprecated events in chromex.ext.idltest namespace.