Marcos Silva

In order to have more than one client, Hubi would benefit to have an adapter layer between the external world and its use cases

This could be React client where a server some documents are read in order to create the client's domain model

Migrate the current CLI to the correct layer (according to Clean Architecture)

There should be a clear layer separation between what's part of Hubi's domain and what is part of its use cases

Setting a string as non-required don't allow to use `null`s as its value # Enviroment * MacOS [email protected] * [email protected] # How to reproduce ```yml name: Foo attributes: - name:...

Values could be limited to a certain amount of enumerated values Keep in mind that in some languages, those values are like tokens themselves, while in others they are just...

With a simple validation as a decorator for [attribute](https://mvcds.github.io/hubi/#attribute), it is possible to be sure of consistent values across the different domains using Hubi

Having default values exported would allow other code to reference them, making easy to not repeat writing code

Allow hubi to use decorators (from #106) which are not in this same repository. For instance, configuring a required string to have a max length of 30 digits in a...

The domain file guide states the following about [decorators](https://github.com/mvcds/hubi/blob/master/docs/domain-file-guide.md#decorators) > Each attribute type may have some decorators associated with it, enhancing how they are translated. But the only decorator in...