Expose internal.ts to public to easily extend EntityState using same logic

[ngxs-labs]

Expose internal.ts to public to easily extend EntityState using same logic

[splincode]

With the action aproach this is not a problem because you will dispatch actions, and you will not have the state as depency.

here I will not help you with anything, use native NGXS

But in general, if you were to use even regular services (rxjs statefull) instead of NGXS, this is a bad approach to have circular dependencies

[splincode]

@AM4Apps Today, full attention is paid to the new project and plugin:
https://github.com/ngxs-labs/data/blob/master/docs/pages/entity.md

I'm not sure when work on the @ngxs-labs/entity-state plugin will continue

[amollahi]

I check the data plugin.

I guess it works like a data-service, so you need to subscribe yourself if you want to perform the "Action"(method call). ¿Right?

How it will look a FechAll method in the state like this:

public fetchAll(): Observable<any> {
    return this.apiService.fetchAll()
        .pipe(
            tap((array) => this.setEntitiesAll(array))
        );
}

And after you will need to subscribe in the component, ¿Right?

[splincode]

yes

[amollahi]

There's one more thing, ¿how you deal in the ngxs-labs/data plugin with circular dependencies?

If i am not mistaken you should inject other states to call their methods or to join data from multiple states.

State A => Call State B method(Action)
State B => Call State A method(Action)

or

State A selector get data from State B
State B selector get data from State A

[splincode]

please create stabcklitz example

[amollahi]

Whould be easier with a more specific model:

export interface IAuthorDTO {
    avatar?: string;
    bornDate?: Date;
    idLocation?: number;
    id?: number;
    name?: string;
}

export interface ILocationDTO {
    authorsIds?: number[];
    city?: string;
    country?: string;
    id?: number;
}

What i am trying is:

• Fetch some of the Authors to AuthorState
  • if i don't have in the store the "Location"(idLocation) of an author call LocationState FechById
• After Join Both States in a Selector to represent Author with the associated Locations

And the other way:

• Fetch some of the Locations to LocationState
  • if i don't have in the store the "Author"(authorsIds[]) of a location call AuthorState FechById
• After Join Both States in a Selector to represent Locations with the associated Authors

Result
So the dependencies should be like this:

• AuthorState: should have LocationState and ApiAuthorService
• LocationState : should have AuthorState and ApiLocationService

---

With the action aproach this is not a problem because you will dispatch actions, and you will not have the state as depency.

[amollahi]

Ok thanks, i thought that.

I was checking to work with normalized data with NGXS similar to this Akita Normalized Data