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.
As proposed in #279.
Before:
After:
The property system is inspired by WPF dependency properties + freezable objects approach.
However, there are restrictions made to maintain compatibility with the current codebase:
Characteristic
) can be used only once per object instance (no way to assign different values forJob.Id
andJob.EnvMode.Id
).job.EnvMode
) cannot be null.The expected use-case pattern is
.Apply()
method)Frozen objects are immutable and therefore can be shared across threads or stored in static fields.
Jobs are frozen automatically when added into the config, so the `did we forget to freeze the job?' check is unnecessary.
P.S. Tests are green, suggestions are welcome:)