-
Notifications
You must be signed in to change notification settings - Fork 105
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 invalid pop
directives
#184
Conversation
- `pop` only accepts `true` or a positive integer larger than zero.
@willrowe we should target a specific version of sublime (within packages.json) for this change to retain backward compatibility I think. Comments say it was "ignored" before but to be safe I think I rather mark this change as a forward only change. Can you add the specific build numbers with >= in packages? |
I don't use this package but just wonder what's the point of using/keeping |
Are we 100% certain it does nothing in ST3? If we are or can find a document example (or proven test) that this is indeed true I am willing to make the change. However if we are not then it's much more risky to let this flow backwards when it has worked this way for years. |
I believe it would be best to fix this for ST3, even though it technically works by being ignored.
I defer to you, of course, if you would still like me to add the version constraint. |
Ahh perfect, this is enough to convince me we can safely remove it. Thanks! |
Thanks for the contributions! |
Thanks for taking a look at this @Medalink, really appreciate the package! |
pop
only acceptstrue
or an integer larger than zero.The invalid directives break the syntax in pre-release builds of Sublime. The syntax would not even be loaded. This will ensure compatibility going forward.