PaginationState not exported

[tklingert]

Hi,

Scenario:

• User can dynamically define data views.
  A DataViewDefinition holds information about the view's name, fields & it's key field.
• As a basic feature, the user needs to be able search within and results should be returned using pagination.

Solution approach:

• Create a dedicated store per view from the definition on demand to manage the state.

   function createViewStore(definition: DataViewDefinition) {
    return createStore(
      { name: `dataView_${definition.Name}` },
      withEntities<DataViewRecordEntity<string>, string>({ idKey: definition.primaryKey }),
      withPagination({ initialPage: 1 }),
      ...
    );
  }

• Expose a facade to the application and encapsulate the store within.

Issue:

• As the code gets more complex, I would like to structure it & split it across multiple files and avoid a single huge file which contains everything related to the state & it's management.
  ->
  At some point, I need to export the store to be able to use it internally from within other files.
  But since the PaginationState is not exported, I'm ending up with:
  • Return type of exported function has or is using name 'PaginationState' from external module "node_modules/@ngneat/elf-pagination/lib/pagination" but cannot be named.ts(4058)

Is the pagination state intentionally kept internally ?
Am I maybe missing any other obvious way, which wouldn't leave me behind with a single huge file ?

Thanks !

[NetanelBasal]

No. You are welcome to create a PR that exports it

[tklingert]

Thanks, I've added a pull request.