Double initialisation?

[alexbainbridge]

Double initialisation?

[trakhimenok]

I see same duplicate log records.

[chron0]

Dito, and, although not yet confirmed with empirical tests, I'd also agree on the sentiment that ionic-storage pulls heavy on startup time. When I used native localstorage before, it seemed way faster. But since localstorage is not an option for certain platforms/deployments it would be great to see ionic-storage perform at a similar level (ionickv/indexdb).

[chron0]

There is some other oddity I've discovered when setting a different db/store name (other than the default _ionickv), which may have the same origin:

export function provideStorage(): any {
  return new Storage(
    [
      'sqlite',
      'indexeddb',
      'websql',
      'localstorage',
    ],
    {
      name: 'governessdb',
      storeName: 'governessdata',
    }
  );
}

[...]

export function providers(): any {
  return [
    [...]
    // Enable Ionic's storage engine
    { provide: Storage, useFactory: provideStorage },
  ];
}


@NgModule({
  [...]
  providers: providers(),
})

It still creates the _ionickv indexeddb and now half of the data is in _ionickv, while other stuff, which was triggered to write later (after init) within the applications workflow is in governessdata.

Code: https://github.com/apollo-ng/governess/tree/master/client

[mlynch]

Hmm, not able to reproduce

[chron0]

@mlynch: Thanks for the reminder. Since you couldn't reproduce I went ahead and tried to figure it out. I haven't done a second round to re-verify but in my case it seemed to have been caused by wrapping ionic-storage into a storage provider/service and then using this in the actual data provider services.

Before there was ionic-storage I created my own storage provider to wrap native localstorage and after ionic-storage was released I just swapped my localstorage calls with ionic-storage ones.

After importing and using ionic-storage in each data provider/service instead of my own storage provider it creates only the governessdata storage instance. I have no idea why it should make a difference but it seems to do.

[mhartington]

Closing!