feat: Allow users to opt out of compat aliases #79
Conversation
src/index.ts
Outdated
| * Whether to use preact/compat aliases | ||
| * @default true | ||
| */ | ||
| compatAliasesEnabled?: boolean; |
There was a problem hiding this comment.
Alternatively, preactCompatAliasesEnabled? Not sure what's best, open to suggestions
There was a problem hiding this comment.
I'd also be fine with reactAliases: boolean since it's shorter. Technically we're not aliasing compat to something but rather react to compat.
There was a problem hiding this comment.
That's true. I suppose we could also go compatEnabled; the end user is probably just looking at enabling/disabling compat, do they need to know it's done via aliases? Just a thought.
I do like having ...Enabled in the name, though -- matches the prefresh & devtools options and is also a bit more obvious that it's a boolean from a naming perspective.
rschristian
force-pushed
the
feat/compat-aliases-option
branch
from
02efaf0
to
b691ac3
Compare
rschristian
force-pushed
the
feat/compat-aliases-option
branch
from
b691ac3
to
5136e05
Compare
|
Hi, how would I be able to get ahold of this? The latest version is 2.5.0 which was released before this change went in. I'm also not seeing a pre-release version? Thanks! |
|
@jschuler You can patch your |
Closes #78