You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While messing around with some components, an issue arose when using Component#font(Key) on its own outside of builders. It doesn't respect the initial provided component type in it's returned output.
EDIT: after a bit more messing around these are all the effected methods
Fusezion
changed the title
Component#font doesn't respect initial component type
ScopedComponent doesn't always respect initial component type
Jan 10, 2025
While messing around with some components, an issue arose when using
Component#font(Key)
on its own outside of builders. It doesn't respect the initial provided component type in it's returned output.EDIT: after a bit more messing around these are all the effected methods
ScopedComponent#font(Key)
,ScopedComponent#style(Consumer<Builder>, Strategy)
,ScopedComponent#appendNewLine()
,ScopedComponent#appendSpace()
,ScopedComponent#applyFallbackStyle(StyleBuilderApplicable...)
,ScopedComponent#applyFallbackStyle(Style)
,ScopedComponent#decorate(TextDecoration....)
,ScopedComponent#decorateIfAbsent(TextDecoration, TextDecoration$State)
,ScopedComponent#decorations(Set<TextDecoration>, boolean)
,ScopedComponent#decorations(Map<TextDecoration, TextDecoration$State>)
,ScopedComponent#replaceText(Consumer<Builder>)
, andScopedComponent#replaceText(TextReplacementConfig)
I've left out the
#compact
method since just like#asComponent
it seems more intentional design wise for it to beComponent
The text was updated successfully, but these errors were encountered: