-
Notifications
You must be signed in to change notification settings - Fork 7
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
Save on the custom page doesn't seem to work, and the custom scripts don't trigger #7
Comments
1.3.5 or HEAD ? |
I'm using a fork from 1.4.0pre (https://github.com/vasili-zolotov/strider) On Fri, Oct 4, 2013 at 4:22 PM, niallo notifications@github.com wrote:
|
does it work in 1.3.5? 1.4.0pre was known to have issues. Hence it was named "pre". |
Ah yes, 1.3.5 works so I guess this is a bug in the pre version. Thank! On Fri, Oct 4, 2013 at 4:40 PM, niallo notifications@github.com wrote:
|
Great. |
Most of the time when I hit save on the strider-custom config page,nothing happens and the script isn't saved.
However, even when I tried using a strider-custom.json file to the root of my project, it still didn't override the existing behavior which runs 'npm test'. Is there something I'm missing here, is strider-custom meant to override the existing behaviors?
The text was updated successfully, but these errors were encountered: