feat: Enhance @Settings macro and enable standalone @Setting usage #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR significantly enhances the macro system to provide more flexibility and better code generation.
Key Changes
Enhanced @Settings Macro
The
@Settingsmacro now generates the same infrastructure asAppSettingValues:Configstruct withOSAllocatedUnfairLockstoreandprefixproperties with getters/settersStandalone @setting Support
@Settingcan now be used without requiring@Settingson the container:Type-Safe Container Resolution
Introduced __ContainerResolver using Swift's conditional conformance:
Automatically detects if container conforms to __Settings_Container
Falls back to UserDefaults.standard with empty prefix if not
Type resolution happens at compile time (zero runtime overhead)
Improved Nested Container Support
Fixed qualified name generation for nested containers:
Correctly generates names like "Profile::setting"
Works for both direct nesting and extension-based nesting
Breaking Changes
None - all existing code continues to work unchanged.