vrenken / etalii.ubigia Goto Github PK

• Formal language definition page.
• Research pages.

• Should we integrate the Diagnostics projects into the core ones?
  Probably not.
• Should we make the diagnostics switchable? If so, how?

• Remove the null metadata error that we can currently have.
• Search for "new Metadata { "
• Most new Metadata creations should be removed as they all relate to the authentication headers.

This and the corresponding PropertyDictionaryJSonConverter_WriteJson_DateTime_Local don't give consistent results on all machines.

It's still unclear if this is a NewtonSoft, timezone or system issue.

• Formal language definition page.
• Research pages.

• Decide on buggy GTL text examples.
• Decide on buggy GCL unit tests.
• Decide on buggy GCL text examples.
• Decide on function @ addition.
• Decide on function replacement of annotation functions.
• Decide on the consolidation of the context and traversal projects.

Having to parse paths after that we have parsed context schema's just doesn't do the trick.

If we want to have subject/sequence powered GCL mappings then we should have integrated parsing/validation as well.

Maybe in the future we should consider consolidating the Context and Traversal projects completely?

• Share visitors using defines.
• Share as much code as possible.
• Antlr GCL + GTL visitor are now one and the same and live in the same project.

Related to #2

• Write a set of query unit tests that fit most use cases.
• Write a set of mutation unit tests that fit most use cases.
• Implement variable scanning.
• Generate parameter codes.
• Align variables in SchemaScope and TraversalScope.

Explain fragments, value fragments & structure fragments:

• Explain optional annotation
• Explain mandatory annotation
• Explain structure fragment plurality

Explain Graph Mapping:

• Explain compact/elaborate mapping
• Explain Value mapping
• Explain plurality mapping

Explain mutations:

• Explain property mutations.
• Explain tag mutations.
• Explain node mutations.
• Explain creating new nodes.
• Explain relation mutations.
• Explain blob mutations.

Aim should be to:

• Not (or minimal) influence the F5 development experience
• Honor the standards set in .NET Core, yet also the structure provided by the Ubigia solution

• Check for correlation Id in the log output of the script parsing/processing.
  It is still not completely correct how the correlation Id's get assigned.
• Add/enable Logging to the infrastructure persistance layer.
• Add/enable Logging to infrastructure fabric layer.
• Fix logging in Api.Logical. Somehow the logical messages are not visible in the centralized logging instance.
• Rename/split ScriptCorrelationId into TraversalCorrelationId and SchemaCorrelationId?

In today's .NET world pattern based switch statements are perfectly fine and able to cope with the complex conditionals needed occasionally. The Selector pattern served its purpose but has become obsolete, therefore it should be removed from the codebase.

• Add unit tests for simple GCL operations.
• Correct plurality on properties and on the result.
• Add comments that explain what traversals will happen.
• Embed the parsed schema into the entity and use it to run the processing.
• Wire up the schemaprocessing on to the result entity.
• Make sure values are adequately mapped.
• Make sure that children are adequately mapped.

• Check for unwanted (personal/business content and remove.
• Validate once more on third party depenendencies (update list?).
• Add source code headers everywhere?
• Prepare for external open source SonarQube instance.

• Move provision into this repository and rename it to ingestion.
• Add CI/CD pipeline that starts Ubigia hosting on one of the server systems.
• Find right candidate(s) application services for ingestion example => Build a list
• Implement ingestion candidate(s) services.

• Research AsyncState
• Add client transport logging to confirm that it should work.
• Add CorrelationId to the Grpc network transport.
• Add CorrelationId to the Grpc service implementations.
• Add CorrelationId to the WebApi network transport.
• Add CorrelationId to the WebApi service implementations.
• Add CorrelationId to the SignalR network transport.
• Add CorrelationId to the SignalR service implementations.
• Make sure all client logging decorators in all layers show up with the CorrelationId instances.

Currently the times are incorrect as the async behavior is not taken into account.

• Make Seq logging internal.
• Make Seq logging in Analyzers conditional

to

Container.RegisterDecorator<TService, TDecorator>()

• Formal language definition page.
• Research pages.

• Add basic GTL Antlr4 definition.
• Add basic GTL Antlr4 unit tests.
• Implement basic sequence parsing.
• Implement full sequence parsing.
• Implement full validation.
• Implement variable parsing.
• Implement function parsing.
• Implement tag parsing.
• Make Parser configurable (i.e. we want to switch back/from Lapa to Antlr.
• Implement general Antlr4 parser.
• Finetune all unit test failures.

• Implement.
• Add parsing+processing examples that mutate the graph.