Colin

Results 10 issues of Colin

Similar to: https://github.com/segmentio/typewriter/issues/91 This issue tracks support for server-side Java clients that are using `analytics-java`, rather than just supporting `analytics-android`.

feature-request
analytics-java

Normally, `typewriter init` looks like this: ![init](https://user-images.githubusercontent.com/2907397/70480253-1d765e00-1a94-11ea-8746-107472716c5c.png) However, on a default Ubuntu terminal, it'll render like this: ![image](https://user-images.githubusercontent.com/2907397/70480083-ab9e1480-1a93-11ea-9a92-4403928f0baa.png) When highlighting text, you'll see that the text is structured correctly, but...

bug

This issue is tracking progress towards supporting Android Java in typewriter 7. `analytics-android` support is currently available via Typewriter 6 (`npm install [email protected]`).

feature-request
analytics-android

This issue tracks progress towards adding an interactive variant of `typewriter update` that allows you to select which updates to apply, if there are multiple. Currently, when you run `typewriter...

feature-request
cli

In our JS clients, we have a peer dependency on `ajv`, which is used in development builds to apply JSON Schema validation at run-time. In our iOS clients, we don't...

feature-request
analytics-ios

This issue tracks progress towards supporting run-time validation with Common JSON Schemas.

feature-request

Tracking Plans support [versioning of events](https://segment.com/docs/protocols/tracking-plan/#tracking-plan-event-versioning) through a `context.protocols.event_version` field, which is an integer (defaulting to `1`) that determines which version of an event schema to apply. This is oftentimes...

feature-request

We have some [internal contributing docs for typewriter](https://paper.dropbox.com/doc/typewriter-Typewriter-Architecture--Aor9UZIO8VnJvFDlQnaGnoXCAg-50qWA8xC3JSzlb1Y7vGHq), but we should flesh out that document and move it into this repo, under a `CONTRIBUTING.md` so that we can enable external...

feature-request

Consider the following field: ``` body: '{ "id": "ev123" }' ``` Since this value includes double quotes, wrapping the string in double quotes would require escaping: ``` body: "{ \"id\":...

```yaml # test.yaml actor: group.Sync options: contexts: "test-context.yaml" acts: - actor: misc.Note options: message: "{CONTEXT_VALUE|Default Value}" ``` ```yaml # test-context.yaml - CONTEXT_VALUE: "Hello World" ``` This outputs `"Default Value"` instead...

bug