Currently the name of the preferences is fetched from the class:

@SuppressWarnings("unused")
@SharedPref(SharedPref.Scope.UNIQUE)
public interface SessionStore {

    String sessionId();
}

This creates a preferences file "SessionStore". This can cause the following errors:

The Preferences are lost when a refactoring renames the class
The Preferences could conflict with a "SessionStore" preferences used in another module

To cirumvent the following I'd like to specify the name of the session store manually:

@SuppressWarnings("unused")
@SharedPref(name="MyNamedPreferencesFile")
public interface SessionStore {

    String sessionId();
}

This way the refactoring error is eliminated. The naming conflict could persist but can be easily cirumvented.

My personal use cases are the following:

Eliminating the possible refactoring bug. Because refactoring is done quiet regularly on a large scale app.
Using the AA Preference system on legacy preference files that were created without using AA.

Additionally, supporting non-constant naming of the preferences file would be usefull. Something like:

SessionStore_.from("UserPreferences"+userId)...

Could serve the same interface for different preference files.

@SharedPref dynamic naming #1675

Description