how can I expose the selectors used to create extraSelectors with createFeature?

[naticaceres]

I am working on a feature where I need to expose a raw version of the state along with a refined version of the state.

i.e. when creating a store for auth with a state as described below, I'd like to expose both selectUser (that is provided by createFeature), and selectIsLoggedIn (that is an extraSelector derived from selectUser)
this is what my code looks like:

interface AuthState {
  user: {
    email: string;
    metadata: any;
  } | null;
  isLoaded: boolean;
}

const initialState: AuthState = ...

export const authFeature = createFeature({
  name: 'auth',
  reducer: createReducer(initialState),
  extraSelectors: ({ selectUser }) => ({  // ERROR 'selectUser' is already declared in the upper scope
    selectIsLoggedIn: createSelector(selectUser, user=> !!user)
  })
});

export const { name, reducer, selectUser, selectIsLoggedIn} = authFeature

the problem is,I cannot export selectUser bc it complains in the createFeature function param about selectUser being declared in an upper scope.

my solution for now has been to redefine selectUser in extraSelectors with a different name, and expose that.

export const authFeature = createFeature({
  name: 'auth',
  reducer: createReducer(initialState),
  extraSelectors: ({ selectUser }) => ({ 
    selectIsLoggedIn: createSelector(selectUser, user=> !!user),
    selectUser_: createSelector(selectUser, user=> user) // now it works
  })
});

export const { name, reducer, selectUser_, selectIsLoggedIn} = authFeature

is there a big problem with this situation that I am missing, or is there a pattern I should be looking into to avoid this alltogether?
or else, what is the proper way to expose the raw feature selector along the extraSelectors derived from it?

edit1: reworded for clarity