FxMap.MongoDb 4.1.1

<p align="center"> <img src="https://raw.githubusercontent.com/quyvu01/FxMap/main/FxMap.png" alt="FxMap" width="96" /> </p>

<h1 align="center">FxMap.MongoDb</h1>

<p align="center"> MongoDB data provider for FxMap — answers FxMap requests straight from your collections. </p>

<p align="center"> <a href="https://www.nuget.org/packages/FxMap.MongoDb"><img alt="NuGet" src="https://img.shields.io/nuget/v/FxMap.MongoDb.svg" /></a> <a href="https://www.nuget.org/packages/FxMap.MongoDb"><img alt="Downloads" src="https://img.shields.io/nuget/dt/FxMap.MongoDb.svg" /></a> <a href="https://github.com/quyvu01/FxMap/blob/main/LICENSE"><img alt="License" src="https://img.shields.io/badge/license-Apache--2.0-blue.svg" /></a> </p>

<p align="center"> <a href="https://github.com/quyvu01/FxMap"><b>FxMap</b></a> · <a href="https://fxmapper.net"><b>Documentation</b></a> · <a href="https://github.com/quyvu01/TestFxMap-Demo"><b>Demo project</b></a> </p>

The owning service of an entity registers it with EntityConfigureOf<T> and hands FxMap the IMongoCollection<T> that stores it. Incoming requests (ids plus expressions) become one MongoDB query with a BSON projection per distributed key.

Installation

dotnet add package FxMap.MongoDb

Usage

public sealed class UserDistributedKey : IDistributedKey;

public class UserConfig : EntityConfigureOf<User>
{
    protected override void Configure()
    {
        Id(x => x.Id);
        DefaultProperty(x => x.Name);
        UseDistributedKey<UserDistributedKey>();
    }
}

builder.Services.AddFxMap(cfg =>
    {
        cfg.AddEntitiesFromAssemblyContaining<SomeEntityAssemblyMarker>();
        cfg.AddProfilesFromAssemblyContaining<SomeProfileAssemblyMarker>();
    })
    .AddMongoDb(cfg => cfg
        .AddCollection(database.GetCollection<User>("users"))
        .AddCollection(database.GetCollection<Order>("orders")));

Notes

• AddCollection can be chained; register one collection per entity that FxMap should serve.
• Expressions are evaluated against the stored documents, so they use the actual property names of the model (not an ExposedName).
• Ids are parsed to the entity's id type through the same converters as the other providers, including strongly typed ids with an IStronglyTypeConverter<TId>. As of 2.3.5 a response is also answered under the id text that was sent. That match compares the text of the stored _id with the text of the parsed id, so an id type whose BSON text form differs from ToString() is not matched. Test your id type.

Related packages