-
Notifications
You must be signed in to change notification settings - Fork 0
Issues: jsdevel/XforJS
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
closure is obfuscating constructor names making for unreadable output errors.
bug
#65
opened Jul 29, 2013 by
jsdevel
templates shouldn't be required if import statements exist.
deprecation
#64
opened Jul 29, 2013 by
jsdevel
A default config file should be created when no config file is found.
enhancement
#63
opened Jul 17, 2013 by
jsdevel
The filename should be given on failures from the CLI.
enhancement
#62
opened Jul 17, 2013 by
jsdevel
space isn't preserved between opening {foreach} and text when normalizespce=>false.
bug
#57
opened Jun 25, 2013 by
jsdevel
rename "xforjsOptions" to just "options" in the config file.
deprecation
#56
opened Jun 25, 2013 by
jsdevel
running $(npm bin)/xforjs: AMD appears in error message when AMD isn't true.
bug
#55
opened Jun 25, 2013 by
jsdevel
Sort should convert non string / numeric / object values to 1 or 0 depending on 'truthiness'
bug
#38
opened May 23, 2013 by
jsdevel
The '^' symbol may allow XforJS internal variables to conflict with outer variables.
bug
#37
opened May 21, 2013 by
jsdevel
Provide a way to avoid calling eval in the current block.
enhancement
#28
opened Mar 9, 2013 by
jsdevel
ProTip!
Follow long discussions with comments:>50.