Skip to content

Fix typo in export-to-javascript.md #551

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jun 20, 2021
Merged

Fix typo in export-to-javascript.md #551

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/interoperability/export-to-javascript.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -182,7 +182,7 @@ followed by the JavaScript export name.

While an `@JSExport`ed method inside an `@JSExportTopLevel` object allows JavaScript code to call a "static" method,
it does not feel like a top-level function from JavaScript's point of view.
`@JSExportTopLevel` can also be used directory on a method of a top-level
`@JSExportTopLevel` can also be used directly on a method of a top-level
object, which exports the method as a truly top-level function:

{% highlight scala %}
Expand Down