## [protons-v6.0.2](protons-v6.0.1...protons-v6.0.2) (2023-01-12)

### Dependencies

* remove lerna, update aegir ([#76](#76)) ([83a24f2](83a24f2))

You can now use maps:

```protobuf
message MapTypes {
  map<string, string> stringMap = 1;
}
```

They are deserlialized as ES6 `Map`s and can support keys of any type
- n.b. protobuf.js deserializes maps as `Object`s and only supports
round tripping string keys.

## [protons-v6.1.0](protons-v6.0.2...protons-v6.1.0) (2023-01-12)

### Features

* add support for maps ([#75](#75)) ([e8dfc0a](e8dfc0a))

Empty messages should be supported

## [protons-v6.1.1](protons-v6.1.0...protons-v6.1.1) (2023-01-17)

### Bug Fixes

* support empty messages ([#78](#78)) ([8a02910](8a02910))

`required` is a field in proto2 but not in proto3 so throw if it
is encountered while generating `.ts` from `.proto`.

It would be better to detect `proto2` from the `syntax` directive
but it's not in the output of the `pbjs -t json` command.

Fixes #34

## [protons-v6.1.2](protons-v6.1.1...protons-v6.1.2) (2023-01-31)

### Bug Fixes

* throw when unsupported fields are detected ([#80](#80)) ([8108875](8108875)), closes [#34](#34)

Refuse to compile an empty .proto file

## [protons-v6.1.3](protons-v6.1.2...protons-v6.1.3) (2023-01-31)

### Bug Fixes

* throw when .proto is empty ([#81](#81)) ([ed392cb](ed392cb))

To allow regenerating good fixtures, move the bad fixtures to
their own directory.

As per [`proto3`'s language guide](https://developers.google.com/protocol-buffers/docs/proto3#specifying_field_rules):

> Message fields can be one of the following:
>  - singular: a well-formed message can have zero or one of this field (but not more than one). And this is the default field rule for proto3 syntax.

This means that all `proto3` fields are effectively optional when
writing, so it's relatively easy to implement by accepting a `Partial`
version of the message interface for encoding.

When reading messages singular fields are initialized to their default
values when reading and optional values are not so the plain non-`Partial`
interface can be returned.

This also has the nice side effect of not requiring the user to pass
empty lists/maps for `repeated` and `map` fields which never really
felt right.  These values are initialized to their empty forms when
reading messages from the wire.

Fixes #42

ipfs/eslint-config-ipfs#126 will introduce
linting rules on import sorting so order imports during building
in a way that will comply with the new linting rules.

## [protons-runtime-v5.0.0](protons-runtime-v4.0.2...protons-runtime-v5.0.0) (2023-02-02)

### ⚠ BREAKING CHANGES

* singular fields should be optional to write (#83)

### Bug Fixes

* singular fields should be optional to write ([#83](#83)) ([229afbc](229afbc)), closes [#42](#42)
* sort imports ([#84](#84)) ([6f796f1](6f796f1))