when making a custom theme, the theme shape could look like, for example:

colors: {...default RNE colors},
mode: {...default RNE mode},
myCustomColors: {
  text: {
    primary: string;
    secondary: string;
  }
}

when consuming makeStyles for a component, the current implementation of the styles() here ignores any custom fields that have been extended from the FullTheme.

This change proposes returning the full theme so that users have access to their custom/extended themes.

We can extend the Colors itself, IMO, having complete theme object is not necessary for makeStyles
Use never to remove existing colors if they aren't required.

Can you explain further how this would work?

I ask because when we define an extended theme (as per #3450), in our new themed.d.ts file, the custom "theme" name is not a known name (unless RNE adds a specific field to be used for this purpose). I couldn't think how else to guarantee a return of an unknown field name, except to return the entire theme, which is extended off of FullTheme:

declare module '@rneui/themed' {

  export interface FullTheme {
    colors: RecursivePartial<Colors>;
    fluidColors: ColorShape;
  }

}

As you can see below, makeStyles() does not return the full theme since it only returns theme.colors, mode: theme.mode and is missing theme.fluidColors

Can you try #3472 (comment) ?

I understood your point, but what I want to say is, having complete theme object will also contain default Component Props, which I think is overkilling the makestyles, because we only need colors/mode for styling, I believe. Also in your case we only need to add some more colors which can be done by extending Colors.

#3472 solves the issue. thank you