First, TinyBase is awesome, thank you!
Is your feature request related to a problem? Please describe.
In my React Native app, there are some Values that I need to persist and others which must not be persisted (UI-only state).
Describe the solution you'd like
Currently, the store only allows loading subsets of tables by specifying a condition. To provide this feature parity for Values, could we allow an "in-clause" in the DpcTabularValues config? Something like:
values: {
tableName: 'my_tinybase_values',
load: {valuesIn: ['employees', 'open']},
save: {valuesIn: ['employees']},
}Describe alternatives you've considered
The obvious alternative is to create another store for non-persistent values. However, one problem with that approach for me is that the @dev-plugins/tinybase Expo plugin in the React Native app does not support displaying multiple stores at once in the Inspector.
Another alternative is to use a Table with a singleton row to use non-persistent values.
Additional context
I'm using the ExpoSqlitePersister to be specific.
First, TinyBase is awesome, thank you!
Is your feature request related to a problem? Please describe.
In my React Native app, there are some Values that I need to persist and others which must not be persisted (UI-only state).
Describe the solution you'd like
Currently, the store only allows loading subsets of tables by specifying a condition. To provide this feature parity for Values, could we allow an "in-clause" in the
DpcTabularValuesconfig? Something like:Describe alternatives you've considered
The obvious alternative is to create another store for non-persistent values. However, one problem with that approach for me is that the
@dev-plugins/tinybaseExpo plugin in the React Native app does not support displaying multiple stores at once in the Inspector.Another alternative is to use a Table with a singleton row to use non-persistent values.
Additional context
I'm using the
ExpoSqlitePersisterto be specific.