Activities of "aaron"

Features described here: https://github.com/aspnetzero/aspnet-zero-core/issues/347#issuecomment-338776317

Can you try if return new List<> works, instead of holding on to instance variables created in a static constructor?

public static List<SelectItemValue> InitialValues => GetInitialValues();

private static List<SelectItemValue> GetInitialValues()
{
    return new List<SelectItemValue>
    {
        // ...
    }
}

Can you show the relevant methods? Especially: Furiosotoro.Furiosotoro.Migrations.Seed.Host.DefaultSelectItemValuesCreator.AddValueIfNotExists(SelectItemValue value).

No, it's not supposed to be 0.

PR: <a class="postlink" href="https://github.com/aspnetzero/aspnet-zero-core/pull/558">https://github.com/aspnetzero/aspnet-zero-core/pull/558</a>

I do not have any recommendations at the moment. Yes, you should create a custom repository using a library of your choice.

The authSchema parameter was what was causing the problem.

PR: https://github.com/aspnetboilerplate/module-zero-core-template/pull/138

ASP.NET Zero does not provide this out-of-the-box, but you can use other libraries. Related issue: https://github.com/aspnetboilerplate/aspnetboilerplate/issues/648

There are a few ways:

• Check if the CreationTime, LastModificationTime or DeletionTime is not within X period of time.
• Maintain a boolean dictionary somewhere.
• Maintain a boolean property on the Task entity itself. [list:9u85y1vp] [*:9u85y1vp] Add a [NotMapped] property to Task entity:

public class Task : Entity<long>
{
    [NotMapped]
    public bool IsRevisionHandled { get; set; }
}

• Check and set that property when handled:

[UnitOfWork]
public virtual void HandleEvent(EntityUpdatedEventData<Task> eventData)
{
    var task = eventData.Entity;

    if (task.IsRevisionHandled)
    {
        return;
    }

    task.IsRevisionHandled = true;

    // ...
}
```[/*:m:9u85y1vp][/list:o:9u85y1vp]

What you have described is a many-to-one relationship. Can you show relevant code that you use to update an Order?

This issue was fixed in v4.6.0. You can add these 3 lines.