Skip to content

Conversation

@sjrd
Copy link
Member

sjrd commented Feb 15, 2016

Most of these things should be top-level in the package, rather than in the package object.
Basically everything but the implicit pimp of Navigator.

@mseddon
Copy link
Contributor Author

mseddon commented Feb 15, 2016

Doh, good point. I kept the GamepadMappingType literals as final vals in the package though, for lack of a better place to put them (perhaps in a Gamepad companion object, if you feel they should not be in that package).

import scala.scalajs.js
import scala.scalajs.js.annotation.JSName

trait GamepadMappingType
Copy link
Member

Choose a reason for hiding this comment

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

This must extend js.Any.

@sjrd
Copy link
Member

sjrd commented Feb 15, 2016

That's all.

@mseddon
Copy link
Contributor Author

mseddon commented Feb 15, 2016

Updated.

@sjrd
Copy link
Member

sjrd commented Feb 15, 2016

LGTM

sjrd added a commit that referenced this pull request Feb 15, 2016
@sjrd sjrd merged commit 195c54e into scala-js:master Feb 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants