feat: add selector

[aymeric-duchein]

This is a proposition regarding those issues: #3 and #4 .

If this looks good, I'll add the docs. For now you can find an exemple in the spec.ts file.

This allow you to mock every selector* using the mockSelect function. It returns a Subject for each selector allowing you to control in wich order, when and what each selector should emit.
You'll still need to import the NgxsModule.forRoot() module in the Testbed (you'll most likely need it anyway if your component dispatch anything to the store 😉 ) .

*Selectors with parameters should be exported into constant beforehand as function comparison won't recognise them otherwise

[splincode]

What do you think about?

import { mockSelect } from '@ngxs-labs/testing/jest'; // sub package for jest

beforeEach(() => {
        TestBed.configureTestingModule({
            declarations: [HostComponent],
            imports: [CommonModule, NgxsModule.forRoot([ZooState])]
        }).compileComponents();

        foodSelector$ =mockSelect(ZooState.feed);
        animalsSelector$ =mockSelect(ZooState.animals);

        fixture = TestBed.createComponent(HostComponent);
        component = fixture.componentInstance;

        fixture.detectChanges();
    });

[aymeric-duchein]

What do you think about?

import { mockSelect } from '@ngxs-labs/testing/jest'; // sub package for jest

beforeEach(() => {
        TestBed.configureTestingModule({
            declarations: [HostComponent],
            imports: [CommonModule, NgxsModule.forRoot([ZooState])]
        }).compileComponents();

        foodSelector$ =mockSelect(ZooState.feed);
        animalsSelector$ =mockSelect(ZooState.animals);

        fixture = TestBed.createComponent(Hostponent);
        component = fixture.componentInstance;

        fixture.detectChanges();
    });
`

This would be cleaner indeed, a jasmine version would be nice to have now that you mention subpackaging

[splincode]

@aymeric-duchein any progress?

[aymeric-duchein]

Updated with the new Jest sub-package.