Skip to content
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

Remove types from Utils that can be represented by [@mel.unwrap] #60

Merged
merged 3 commits into from
Dec 2, 2024

Conversation

johnhaley81
Copy link
Contributor

This is implementing @liubko's suggestion in this comment.

  • Removes TooltipCursor module
  • Removes StrOrNode module

Both of those can be represented using [@mel.unwrap] which is a 0-cost binding solution.

@liubko
Copy link
Contributor

liubko commented Dec 2, 2024

oh, so StrOrNode was unused 😅

Copy link
Contributor

@liubko liubko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks

@johnhaley81
Copy link
Contributor Author

oh, so StrOrNode was unused 😅

@johnhaley81 johnhaley81 merged commit d5be141 into master Dec 2, 2024
2 checks passed
@johnhaley81 johnhaley81 deleted the use-mel-unwrap branch December 2, 2024 20:19
[@mel.unwrap] [
| `Bool(bool)
| `Obj(
Js.t({
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For closed object type, the definition is just {. "fill": option(string) ...} without the preceding Js.t. I'll fix it in a bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants