Web v1.1.0

Summary

Leveraging OpenTelemetry for distributed tracing and metrics.

Changes since Web v1.0.2

• Added OpenTelemetry dependencies
• Enabled OpenTelemetry tracing
• Enabled Prometheus metrics reporting

CLI v3.2.0

Summary

Leveraging OpenTelemetry for distributed tracing.

Changes since CLI v3.1.1

• Added OpenTelemetry dependencies
• Enabled OpenTelemetry tracing

Backoffice v2.1.0

Summary

Leveraging OpenTelemetry for distributed tracing and metrics.

Changes since Backoffice v2.0.3

• Added OpenTelemetry dependencies
• Enabled OpenTelemetry tracing
• Added manual tracing of transaction file processing
• Enabled Prometheus metrics reporting

Web v1.0.2

Summary

Updated to .NET 7.

Changes since Web v1.0.1

• Updated .NET 7
• Automated dependency updates

Common v2.0.1

Summary

Updated to .NET 7. Common package is now hosted only on GitHub Packages.

Changes since Common v2.0.0

• Updated .NET 7
• Automated dependency updates

CLI v3.1.1

Summary

Updated to .NET 7.

Changes since CLI v3.1.0

• Updated .NET 7
• Automated dependency updates

Backoffice v2.0.3

Summary

Updated to .NET 7.

Changes since Backoffice v2.0.2

• Updated .NET 7
• Automated dependency updates

Web v1.0.1

Summary

Small adjustments, primarily to allow proper file-passing integration with Backoffice. Additionally, Web is now containerized, with a Dockerfile that serves both for code build automation and for image building. Also with the GA release of .NET 5.0, everything has been updated accordingly.

Changes since Web v1.0.0

• Containerized application, resolves #22
• Updated to .NET 5.0 GA
• Made transaction summary output location configurable
• Small code cleanup
• Adjusted default appsettings
• Incremented patch version, now 1.0.1

Resolved Issues

• [Web] Containerize web API project #22

Backoffice v2.0.2

Summary

Some small adjustments made to allow proper integration with Web. Added some unit tests for critical logic, which was severely lacking previously, and required some refactoring for proper mocking of file access. Also, Backoffice is now containerized, with a Dockerfile that serves both for code build automation and for image building. With the GA release of .NET 5.0, everything has been updated accordingly.

Changes since Backoffice v2.0.1

• Containerized application, resolves #23
• Updated to .NET 5.0 GA
• Added step to create empty central services file if not found initially
• Implemented tests for major functional components of Backoffice, resolves #62
• Test mocking assisted by factoring file IO logic out of Parser classes and into a dedicated helper class
• Made TryParseFile method implementation in CentralServicesParser and TransactionSummaryParser more consistent
• Updated to use QIES.Common v2.0.0
• Adjusted default appsettings with new file locations
• Assorted code cleanups
• Incremented patch version, now 2.0.2

Resolved Issues

• [Backoffice] Containerize Backoffice #23
• [Backoffice] Unit tests #62

Web v1.0.0

Summary

For real this time, after the last time was merged incomplete and had to be yanked and relabeled as a beta, the old frontend has now been reimplemented as an ASP.NET Core Web API. As well as many quality improvements, refactorings, and QoL fixes, the main changes include: thorough testing, and completed implementation of the Agent limits from the original project requirements.

Changes since Web v1.0.0-beta

• Updated to .NET 5 RC2
• Moved user id on normal /service requests to X-User-Id header, instead of body field
• Updated dependency to QIES.Common v2.0.0
• Using Common v2 JsonConverters to handle model validation, and conversion to record types at model binding instead of handling it at the controller. Also fixes #29
• Logout request body field now named UserId for consistency. Fixes #24
• Logout now actually checks if user is logged in. Fixes #25
• Removed AllowNull option on ServiceNumberAttribute, no longer needed with new JsonConverters and direct use of record types
• Cleaned up subproject dependency hierarchy
• Fixed incorrect category names in all transaction ILoggers
• Instead of passing request objects through to Transactions, mapping them into new commands
• CreateServiceTransaction now returns TransactionRecord instead of Service for consistency with other Transactions
• ITransaction simplified and made significantly stricter now that all implementations now take a TransactionCommand and return a TransactionRecord. Closes #30
• Implemented Agent limits on change and cancel tickets
• Refactored sell or change tickets flow, splitting the two fully past the controller
• Added logging all along main transaction flows
• Made valid services file location configurable
• Switched to action injection for Transactions to services controller, to simplify constructor
• Renamed users controller path to /api/v1/Users for consistency
• Using Swashbuckle + Redoc + OpenApi customization for API documentation. Also fixes #32
• Enabled JSON log formatter
• Implemented thorough unit tests for QIES.Web and QIES.Core. Resolves #28
• Fixed exception on Forbid responses

Resolved Issues

• [Web] Inconsistent field name in logout request #24
• [Web] Logout should check that provided id is actually logged in #25
• [Web] Test tracking #28
• [Web] NumberTickets model validation should fail with HTTP 400 not 500 #29
• [Web] Simplify ITransaction<TRequest, TResponse> now that TResponse is TransactionRecord in all implementations #30
• [Web] Improve OpenAPI spec for request schemas #32