Need some clarification regarding data portal changes

[Brannos1970]

I am working on understanding the changes to the data portal and need some help.

Firstly, I have the following code in my BusinessBase or similarly in another Base:

public static async Task<CustomerEdit> GetAsync(int customerId) { return await DataPortal.FetchAsync<CustomerEdit>(customerId); }

How do we do this now? We no longer have a constructor, not even a private one, that can get the IDataPortal from DI. Do we need to create IDataPortal in the Task? If so how, as the ApplicationContext is not available in the static methods?

[rockfordlhotka]

Static factory methods are no longer an option.

Your choices are to inject (or create) a DataPortal<T> instance and use it, or put your static factory methods into a factory class (so they become instance methods of that class) and inject the DataPortal<T> into that class.

For the most part, you'll find that your UI elements (page/form/etc.) are created via DI, and so you can just inject the DataPortal<T> you need into the page/form and use it to interact with your domain objects.

[rockfordlhotka]

'factory' is used in different ways.

Are you referring to a factory on the client that calls the data portal, or a factory used to implement the DAL on the server?

[Brannos1970]

Factory used on the client that calls the data portal.

I have a customer with three child objects like below.

[Serializable]
    public class CustomerEdit : BusinessBase<CustomerEdit>
    {
        public AddressEdit MailingAddress
        {
            get => GetProperty(MailingAddressProperty);
            set => SetProperty(MailingAddressProperty, value);
        }

        public static readonly PropertyInfo<AddressEdit> PhysicalAddressProperty = RegisterProperty<AddressEdit>(nameof(PhysicalAddress));

        public AddressEdit PhysicalAddress
        {
            get => GetProperty(PhysicalAddressProperty);
            set => SetProperty(PhysicalAddressProperty, value);
        }

        public static readonly PropertyInfo<CustomerLocations> LocationsProperty = RegisterProperty<CustomerLocations>(nameof(Locations));

        public CustomerLocations Locations
        {
            get => GetProperty(LocationsProperty);
            set => SetProperty(LocationsProperty, value);
        }
}

I assume that for the AddressEdit object I would call 'new AddressEditFactory()' or access through IChildDataportal; but for the CustomerLocations do I create a factory for it and access through the IChildDataPortal or do I just call the CustomerLocationsFactory? Or, do I loop through the data and call the IChildDataPOrtal?

[rockfordlhotka]

Something like this for a simple editable root:

public class CustomerFactory
{
    private IDataPortal<CustomerEdit> CustomerPortal { get; }

    public CustomerFactory(IDataPortal<CustomerEdit> customerPortal)
    {
        CustomerPortal = customerPortal;
    }

    public async Task<CustomerEdit> GetCustomer(int id)
    {
        return await CustomerPortal.FetchAsync(id);
    }
}

[rockfordlhotka]

The rules for how the data portal work haven't changed - you still only use the client-side data portal to interact with root types. Child types are instantiated on the server like normal.

The reason there's an IChildDataPortal<T> is for use in your server-side code. For example, in your CustomerEdit class:

[Fetch]
private async Task Fetch(int id, [Inject]ICustomerDal dal, [Inject]IChildDataPortal<CustomerLocations> locationsPortal)
{
  var customerData = dal.GetData(id);
  var customerLocations = await locationsPortal.FetchChildAsync(id);
}

[Brannos1970]

Excellent, Thank you