Closed Florian-Schoenherr closed 3 years ago
@Florian-Schoenherr I don't see where this is happening. I've reviewed everything that touches the status and currentVersion. The problem would seem to be reflected in the projections and I don't see where.
@hurelhuyag Please put some tracing/logging on this to see where the problem is.
@VaughnVernon There are already log messages appearing for every HTTP request at the INFO level. @Florian-Schoenherr I also noticed the version name removing the issue. It seems it is a UI problem.
@hurelhuyag I meant at other points, especially projections.
BTW, the version assignment is no longer used. I don't know how the UI could do that unless the same version is being defined twice and that latter supersedes the former.
We should remove the event SchemaVersionAssigned
and any code that attempts to handle it. The current and previous versions should be stable/immutable, otherwise changing either could make a big mess.
@VaughnVernon Actually those logs are projection logs. I checked all log messages and HTTP payloads. I didn't find anything wrong on the back-end side.
PS: I added more information on logs https://github.com/vlingo/xoom-schemata/pull/176
@hurelhuyag Perhaps it is simply a data mapping or rendering bug in the UI. /cc @Florian-Schoenherr
I'll take a look, didn't yesterday
probably backend related or recent UI changes