xoom-schemata icon indicating copy to clipboard operation
xoom-schemata copied to clipboard

The VLINGO XOOM Schema Registry.

Results 15 xoom-schemata issues
Sort by recently updated
recently updated
newest added

Currently, all types are generated as subclasses of `DomainEvent`. Other types need to be declared and used in `io.vlingo.schemata.codegen.backend.java.JavaBackend#baseClassOf`

P:2

This is best done as part of #113 Currently, schemata runs on a single node world/stage. To run on `Grid` we need to - [x] Implement `applyRelocationSnapshot` in all entities...

P:1

Currently, most things the UI requires are queried from the backend each time they are required. This includes: - Units - Contexts - Schemata and Schemata Versions - Valid Categories...

Coming from #160, we need to find out what parts of the code still **really** need to be fixed/done. Main priority is what was mentioned in the issue: what was...

Currently creating organizations, units and contexts with the resp. same name is possible. This can lead to them not being distinguishable from the UI. We could either also show the...

Add tests for specifications using nested types, not only basic and computed ones.

We have some ambiguous rules for numbers, i.e. BYTE_LITERAL and DECIMAL_LITERAL, so antlr matches the one that was defined first. In int answer = 42 , it matches the number...

bug
P:1

Use Beanstalk, ECR, or other options best for Kubernetes.

P:1

Currently we only have a backend for generating Java code. We should allow for plugging in additional backends, perhaps via SPI. The following backends have been mentioned in discussions so...

P:2

Example: ``` event SchemaDefined { type eventType timestamp occurredOn version eventVersion string foo string[] bar = {"baz","qux","quux"} int i = 4242 } ``` Resulting code: ``` package io.vlingo.examples.schemata.event; import io.vlingo.lattice.model.DomainEvent;...