This section provides an overview of the improvements, enhancements, and fixes in the v2.3.1 release of the ODS / API. A comprehensive listing of all changes is documented in the Release Notes section.
Hotfix Release - Version 220.127.116.11
A hotfix was released on March 13th, 2018 to address a regression in supporting extensions. See ODS-1863CLOSEDfor more details.
Improvements and Bug Fixes - Version 2.3.1
This release includes updates to incorporate non-breaking changes to support a maintenance release of the Ed-Fi Data Standard (version v2.0.1), plus a number of bug fixes contributed by the Ed-Fi Alliance and implementers.
The Ed-Fi Data Standard v2.0.1 was released in December 2017 to address issues discovered with v2.0 in field use. The changes are entirely non-breaking, additive-only updates, and will have no impact on existing Ed-Fi ODS / API clients. For more information, see Ed-Fi Data Standard v2.0: What's New - Updates and the discussion on ticket ODS-1787 in the Ed-Fi Tracker.
This section briefly describes new features and enhancements built into the ODS / API v2.3 and provides links to additional documentation.
The primary focus of this release is to deliver internal code reorganization and refactoring improvements, that will ease upgrade and migration to future versions. New implementations of the ODS / API should use this release, while existing implementations may choose to wait until there is a need to upgrade.
Source Code Reorganization
Assemblies have been organized around units of deployment rather than technical categories. Among other benefits, this reorganization was required to enable decoupling Ed-Fi ODS / API core components from extension components (ticket ODS-964).
T4 Template Re-engineering
API code generation components were converted to a more robust and maintainable approach. The work involved converting the current T4 templates to Mustache templates, and decoupling API code generation from a direct dependence on the ODS database schema (ticket ODS-1289).
In ODS / API v2.3, we've moved to requiring Visual Studio 2015 as the developer environment (and have deprecated support for Visual Studio 2013). For more information, see Getting Started - Installation Steps (ticket ODS-1271).
Improvements were made to the Swagger experience to display a visual indicator when the Swagger landing page is initializing and an indicator for the current authorization status (tickets ODS-1065, ODS-1146).