Skip to content

Conversation

keijokapp
Copy link
Collaborator

Closes #7

Seems like specifying scroll behavior was always broken. And it wasn't even passed to the DOM API in case of scrollIntoView. I also added missing "instant" scroll behavior option. And Spago files to make local development easier.

Not sure if that's the best way to do it. Seems like a lot of boilerplate and some healthy amount of duplication. In these cases, the data structures (ScrollToOptions and ScrollIntoViewOptions) are simple and all values have static defaults (I presume top and left default to 0.0) so we don't need to use null values. But I don't know how this approach would work in more complicated use cases.

@garyb
Copy link
Member

garyb commented Jan 8, 2024

Thanks!

@garyb garyb merged commit 934a7e9 into master Jan 8, 2024
@garyb garyb deleted the 7-remove-using-ps-internals branch January 8, 2024 12:29
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.

Remove accessing PureScript data model internals from JS
2 participants