Skip to content

Commit 4b3a6d6

Browse files
committed
Removed legacy PropertyConfiguration class
With the `ItemConfiguration` being added as a property to `ItemMetadata` (74cb817), and the mapping services being updated to rely upon `ItemMetadata` to get their configuration data (2f482b1, fe39302), there is no longer a need for the legacy `PropertyConfiguration` class, or to differentiate between item and property differentiation more broadly. Indeed, the main benefit of this was to allow strongly typed access to the `MemberAccessor`, instead of general access to `ItemMetadata`. Since the order if flipped, with `ItemConfiguration` being retrieved _via_ `ItemMetadata` (or `MemberAccessor`), there is always strongly typed access to these objects independent of the configuration object.
1 parent 7c2a790 commit 4b3a6d6

2 files changed

Lines changed: 0 additions & 61 deletions

File tree

OnTopic/Mapping/Internal/ItemConfiguration.cs

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -31,10 +31,6 @@ namespace OnTopic.Mapping.Internal {
3131
/// then the <see cref="ITopicMappingService"/> will instead use the value defined by that attribute, thus allowing a
3232
/// property on the DTO to be aliased to a different property or attribute name on the source <see cref="Topic"/>.
3333
/// </para>
34-
/// <para>
35-
/// The <see cref="ItemConfiguration"/> works with both <see cref="ParameterInfo"/> and <see cref="PropertyInfo"/>
36-
/// instances, whereas the <see cref="PropertyConfiguration"/> works exclusively with <see cref="PropertyInfo"/> instances.
37-
/// </para>
3834
/// </remarks>
3935
internal class ItemConfiguration {
4036

OnTopic/Mapping/Internal/PropertyConfiguration.cs

Lines changed: 0 additions & 57 deletions
This file was deleted.

0 commit comments

Comments
 (0)