Release notes for Version 3.1 #
This release addresses a major issue introduced in version 3.0 related to service layer scoping. In 3.1, we’ve refactored the way services are accessed and scoped, ensuring consistent lifecycle behavior across the platform. This resolves previous issues where services were incorrectly shared or not instantiated as expected in custom environments.
These changes make it easier to manage dependency lifecycles and improve the developer experience when building custom extensions or services within the Elements platform.
🔐 Security Integration for Custom APIs #
\
Custom RESTful APIs can now opt into the Elements security model by setting the following property in your configuration:
@ElementDefaultAttribute("true")
public static final String AUTH_ENABLED = "dev.getelements.elements.auth.enabled";When enabled, this feature enforces full parity with the core Elements authentication system. Your custom endpoints will inherit:
- Session token verification
- User authentication
- Permission enforcement
This allows developers to extend the backend securely without duplicating or rewriting auth logic.
Additional Fixes and Enhancements #
- Improved validation and error reporting for service injection configuration
- Extended documentation for custom API and middleware development
- Minor performance optimizations in the request routing pipeline
- Fixed a bug related to deleting user accounts
- Added OAuth 2.0 support for Steam APIs