Add a new schematic to generate:

A service that extends ComponentStore
A spec file if requested
Maybe an inlined interface for the default type

Describe any alternatives/workarounds you're current

🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑

hi, im using selector of ngxs, and our team create a dynamic selector, inside of documentation we didn't see nothing about this, but we´re asking if this is a good practice. Here´s the example of how we doit
`
@selector()
static current_answers(state: QuestionnaireStateModel): {getBy: (questionId: number) => number[]} {
return {getBy: (questionId: number)

Implement all functionality of reports module for mobile platforms

Open call to our awesome community to help create documentation. If interested please work with us here and extend the existing docs for the scenarios you need.

This should fail because otherNum is not part of the State interface:

interface State {
  num: number
}

export const initialState: State = {
  num: 0
};

export const appsReducer = createReducer(initialState, handleAction => [
  handleAction(actions.getApps.success, () => ({
    num: 0,
    otherNum: 0 // adding this property should trigger a warning
  })),
]);