Skip to content

Separate Projects #34

@JeremyCaney

Description

@JeremyCaney

Currently, a number of implementations which aren’t required by the core OnTopic library are included in the OnTopic project. We should consider migrating these to separate projects (and, thus, packages) within the same repository, similar to e.g., SqlTopicRepository.

Obviously, the interfaces, base classes, and any shared classes would remain in the OnTopic project.

Candidates

  • (Cached)TopicMappingService
  • (Cached)HierarchicalTopicMappingService
  • ReverseTopicMappingService

Positively, this would better separate ancillary libraries. Negatively, it would increase the number of packages, even though most would be needed by typical projects, and it’s unlikely that we’d end up with alternate implementations that might need to be swapped out.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area: MappingRelates to one of the `ITopicMappingService` interfaces or implementations.Area: PackagesRelates to packaging the library as a NuGet package.Status 0: DiscussionNeeds further evaluation of requirements and prioritization.Type: ImprovementImproves the functionality or interface of an existing feature.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions