Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@ovotech/avro-ts

Package Overview
Dependencies
Maintainers
149
Versions
33
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@ovotech/avro-ts

Convert avro schemas into typescript interfaces

  • 4.2.3
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
29K
decreased by-20.1%
Maintainers
149
Weekly downloads
 
Created
Source

Avro TS

Generate typescript from avro types.

Uses typescript's compiler api to convert avro to typescript AST, and pretty prints the results.

Using

yarn add @ovotech/avro-ts

And then you can use the function to get typescript types:

examples/simple.ts

import { toTypeScript } from '@ovotech/avro-ts';
import { Schema } from 'avsc';

const avro: Schema = {
  type: 'record',
  name: 'User',
  fields: [
    { name: 'id', type: 'int' },
    { name: 'username', type: 'string' },
  ],
};

const ts = toTypeScript(avro);

console.log(ts);

Resulting TypeScript:

export type AvroType = User;

export interface User {
  id: number;
  username: string;
}

Logical Types

Avro has logical types. In their docs:

The built-in types provided by Avro are sufficient for many use-cases, but it can often be much more convenient to work with native JavaScript objects.

To support them we need to modify the typescript generation to use the typescript type instead of the logical type. If we don't avro-ts will fall back on the original underlying type.

examples/logical-types.ts

import { toTypeScript } from '@ovotech/avro-ts';
import { Schema } from 'avsc';

const avro: Schema = {
  type: 'record',
  name: 'Event',
  fields: [
    { name: 'id', type: 'int' },
    { name: 'createdAt', type: { type: 'long', logicalType: 'timestamp-millis' } },
  ],
};

const ts = toTypeScript(avro, {
  logicalTypes: {
    'timestamp-millis': 'string',
  },
});

console.log(ts);

Resulting TypeScript:

export type AvroType = Event;

export interface Event {
  id: number;
  createdAt: string;
}

We can also use custom classes for our logical types. It will also add the code to import the module.

examples/custom-logical-types.ts

import { toTypeScript } from '@ovotech/avro-ts';
import { Schema } from 'avsc';

const avro: Schema = {
  type: 'record',
  name: 'Event',
  fields: [
    { name: 'id', type: 'int' },
    { name: 'decimalValue', type: { type: 'long', logicalType: 'decimal' } },
    { name: 'anotherDecimal', type: { type: 'long', logicalType: 'decimal' } },
  ],
};

const ts = toTypeScript(avro, {
  logicalTypes: {
    decimal: { module: 'decimal.js', named: 'Decimal' },
  },
});

console.log(ts);

Resulting TypeScript:

import { Decimal } from 'decimal.js';

export type AvroType = Event;

export interface Event {
  id: number;
  decimalValue: Decimal;
  anotherDecimal: Decimal;
}

Wrapped Unions

Avro Ts attempts to generate the types of the "auto" setting for wrapped unions. https://github.com/mtth/avsc/wiki/API#typeforschemaschema-opts This would mean that unions of records would be wrapped in an object with namespaced keys.

The typescript interfaces are also namespaced appropriately. Avro namespaces like 'com.example.avro' are converted into ComExampleAvro namespaces in TS.

examples/wrapped-union.ts

import { toTypeScript } from '@ovotech/avro-ts';
import { Schema } from 'avsc';

const avro: Schema = {
  type: 'record',
  name: 'Event',
  namespace: 'com.example.avro',
  fields: [
    { name: 'id', type: 'int' },
    {
      name: 'event',
      type: [
        {
          type: 'record',
          name: 'ElectricityEvent',
          fields: [
            { name: 'accountId', type: 'string' },
            { name: 'MPAN', type: 'string' },
          ],
        },
        {
          type: 'record',
          name: 'GasEvent',
          fields: [
            { name: 'accountId', type: 'string' },
            { name: 'MPRN', type: 'string' },
          ],
        },
      ],
    },
  ],
};

const ts = toTypeScript(avro);

console.log(ts);

Which would result in this typescript:

/* eslint-disable @typescript-eslint/no-namespace */

export type Event = ComExampleAvro.Event;

export namespace ComExampleAvro {
  export const ElectricityEventName = 'com.example.avro.ElectricityEvent';
  export interface ElectricityEvent {
    accountId: string;
    MPAN: string;
  }
  export const GasEventName = 'com.example.avro.GasEvent';
  export interface GasEvent {
    accountId: string;
    MPRN: string;
  }
  export const EventName = 'com.example.avro.Event';
  export interface Event {
    id: number;
    event:
      | {
          'com.example.avro.ElectricityEvent': ComExampleAvro.ElectricityEvent;
          'com.example.avro.GasEvent'?: never;
        }
      | {
          'com.example.avro.ElectricityEvent'?: never;
          'com.example.avro.GasEvent': ComExampleAvro.GasEvent;
        };
  }
}

Notice that not only the interfaces themselves are exported, but their fully qualified names as well. This should help to improve readability.

We also breakout the root type from its namespace for ease of use.

import { ComExampleAvro as NS, Event } from '...';

const elecEvent: Event = {
  id: 10,
  event: { [NS.ElectricityEventName]: { MPAN: '111', accountId: '123' } },
};

const gasEvent: Event = {
  id: 10,
  event: { [NS.GasEventName]: { MPRN: '222', accountId: '123' } },
};

Running the tests

Then you can run the tests with:

yarn test

Coding style (linting, etc) tests

Style is maintained with prettier and tslint

yarn lint

Deployment

Deployment is preferment by lerna automatically on merge / push to master, but you'll need to bump the package version numbers yourself. Only updated packages with newer versions will be pushed to the npm registry.

Contributing

Have a bug? File an issue with a simple example that reproduces this so we can take a look & confirm.

Want to make a change? Submit a PR, explain why it's useful, and make sure you've updated the docs (this file) and the tests (see test folder).

License

This project is licensed under Apache 2 - see the LICENSE file for details

FAQs

Package last updated on 16 Jul 2020

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc