Skip to content
This repository was archived by the owner on Mar 10, 2021. It is now read-only.

is there a reason why "World" is global? #25

Open
sysl-dev opened this issue Oct 17, 2019 · 0 comments
Open

is there a reason why "World" is global? #25

sysl-dev opened this issue Oct 17, 2019 · 0 comments

Comments

@sysl-dev
Copy link

Is there a reason why World is a global in the Windfield library? I changed it to a local in the library without anything appearing to break. So I wanted to confirm.

idbrii added a commit to idbrii/love-windfield that referenced this issue Jul 3, 2021
Fix a327ex#25.

BREAKING: Users who dependent on this global will need to define it
themselves.
    World = require('windfield').World

Don't pollute globals with our type. You're not likely to access World
often -- you'll use the instance it creates instead.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant