-
Notifications
You must be signed in to change notification settings - Fork 1
fix: improve type guard correctness #35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Resolves #30 .
| ); | ||
| } | ||
|
|
||
| export type EditEvent<E extends Edit = Edit> = CustomEvent<E>; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why have you removed this? As I understand it, the only way we will see EditV1 objects is if they come from Plugins which have not yet made the switch, they will therefore come as events. If we're removing event support for EditV1, then everything else v1 related is probably superflous.
Would you consider restoring this and adding the associated:
declare global {
interface ElementEventMap {
['oscd-edit']: EditEvent;
}
}
I would very much like to support EditV1 in the shell for now. I'm all on for plastering depricated notices everywhere on this and adding console.warn()'s, but I'd very much like to make the adoption of oscd-shell, as friendly as is practical.
stee-re
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!!
Also, add OpenEvent.
Also, add some documentation.
Also, remove wizards from the markdown API doc.
Also, move utils to a separate module.
Also, expose the module members that were still missing.
Sorry for the big pull request.