Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / featurist/pogoscript issues and pull requests
#66 - Bump uglify-js from 2.4.24 to 3.6.8
Pull Request -
State: open - Opened by dependabot[bot] over 4 years ago
Labels: dependencies
#65 - Setting a variable to if
Issue -
State: closed - Opened by skistaddy about 5 years ago
- 2 comments
#64 - Fixing letter transposition typo in Continuations
Pull Request -
State: closed - Opened by acook over 8 years ago
- 1 comment
#63 - Destructuring assignments?
Issue -
State: open - Opened by 00dani almost 9 years ago
- 3 comments
#62 - make bluebird a dependency
Pull Request -
State: closed - Opened by charlierudolph almost 9 years ago
- 6 comments
#61 - End of line comment parse error
Issue -
State: open - Opened by joshski about 9 years ago
- 2 comments
#60 - peer dependency needs to become dependency
Issue -
State: closed - Opened by charlierudolph about 9 years ago
#59 - Update the Ruby gem
Issue -
State: open - Opened by joshski over 9 years ago
#58 - compiling with { inScope: false } causes variable redefinition bug
Issue -
State: open - Opened by joshski over 9 years ago
#57 - Improved error message when using promise keyword inapropriately
Issue -
State: open - Opened by adiel over 9 years ago
- 1 comment
#56 - Unexpected token: keyword (debugger)
Issue -
State: open - Opened by artemave over 9 years ago
#55 - object with comments raises parse error
Issue -
State: closed - Opened by adambene over 9 years ago
- 1 comment
#54 - JSHint compatibility
Issue -
State: open - Opened by adambene over 9 years ago
#53 - unexpected parse error
Issue -
State: open - Opened by artemave over 9 years ago
- 4 comments
#52 - community, management
Issue -
State: open - Opened by adambene over 9 years ago
- 1 comment
#51 - async docs are outdated
Issue -
State: closed - Opened by adambene almost 10 years ago
- 1 comment
#50 - pogoscript maturity, reliability
Issue -
State: closed - Opened by adambene almost 10 years ago
- 1 comment
#49 - adds an example of how to do javascripts `for in`
Pull Request -
State: closed - Opened by dereke almost 10 years ago
- 1 comment
#48 - new promisify
Issue -
State: open - Opened by refractalize almost 10 years ago
- 1 comment
#47 - operator followed by indented section
Issue -
State: open - Opened by refractalize almost 10 years ago
#46 - Better error reporting when assining to macros
Issue -
State: open - Opened by refractalize almost 10 years ago
- 1 comment
#45 - x @or x = expr
Issue -
State: open - Opened by refractalize about 10 years ago
#44 - require in repl
Issue -
State: closed - Opened by refractalize about 10 years ago
#43 - Missing link to github repo on new website
Issue -
State: closed - Opened by artemave about 10 years ago
- 7 comments
#42 - Method chaining docs seems to be incorrect
Issue -
State: open - Opened by artemave about 10 years ago
#41 - list comprehensions don't close over variables
Issue -
State: closed - Opened by refractalize about 10 years ago
#40 - String interpolation windows vs nix
Issue -
State: closed - Opened by dereke over 10 years ago
#39 - Async commands in repl
Issue -
State: closed - Opened by joshski over 10 years ago
#38 - async functions with futures don't call callback
Issue -
State: closed - Opened by refractalize over 10 years ago
#37 - Update 2013-12-07-concurrency-patterns.md
Pull Request -
State: closed - Opened by dereke over 10 years ago
#36 - fix pogo.lex()
Pull Request -
State: closed - Opened by joshski over 10 years ago
#35 - Angular JS Cheatsheet
Pull Request -
State: closed - Opened by dereke over 10 years ago
#34 - return ! (result)
Issue -
State: closed - Opened by joshski over 10 years ago
- 4 comments
#33 - interscope variable name collision?
Issue -
State: closed - Opened by artemave over 10 years ago
- 13 comments
#32 - splat arguments to async method calls
Issue -
State: closed - Opened by refractalize over 10 years ago
#31 - Is this supposed to work?
Issue -
State: closed - Opened by ghost over 10 years ago
- 4 comments
#30 - could you think about that variables can support unicode?
Issue -
State: closed - Opened by NoGeneral over 10 years ago
- 3 comments
#29 - allow *** inside c++ style comments
Pull Request -
State: closed - Opened by joshski almost 11 years ago
- 1 comment
#28 - Three contiguous stars in multi-line comments confuse compiler
Issue -
State: closed - Opened by adiel almost 11 years ago
#27 - cannot call blocks
Issue -
State: closed - Opened by refractalize about 11 years ago
- 1 comment
#26 - Wanted, anonymous function syntax with parameters
Issue -
State: open - Opened by PhilAndrew about 11 years ago
- 2 comments
#25 - Order of parameters not preserved
Issue -
State: closed - Opened by PhilAndrew about 11 years ago
- 2 comments
#24 - REPL doesn't work in Node 0.10
Issue -
State: closed - Opened by refractalize over 11 years ago
- 1 comment
#23 - Cannot return from inside for/in loop
Issue -
State: open - Opened by adiel over 11 years ago
#22 - optional arguments cannot be initialised with async expressions
Issue -
State: open - Opened by refractalize over 11 years ago
#21 - optional parameters aren't in scope
Issue -
State: closed - Opened by refractalize over 11 years ago
#20 - switch statements?
Issue -
State: open - Opened by dubiousdavid over 11 years ago
- 1 comment
#19 - Example Fix
Issue -
State: closed - Opened by dubiousdavid over 11 years ago
- 1 comment
#18 - Catch Compile Exceptions
Issue -
State: open - Opened by dubiousdavid over 11 years ago
#17 - "bare" option
Issue -
State: open - Opened by dubiousdavid over 11 years ago
- 1 comment
#16 - Multi-line Strings
Issue -
State: closed - Opened by dubiousdavid over 11 years ago
- 1 comment
#15 - REPL ReferenceError: continuation is not defined
Issue -
State: closed - Opened by joshski over 11 years ago
- 1 comment
#14 - nested comments shouldn't nest, but they do
Issue -
State: closed - Opened by refractalize over 11 years ago
#13 - async ! operator up against a comma
Issue -
State: closed - Opened by adiel over 11 years ago
- 2 comments
#12 - interactive: variables are not assigned from async expressions
Issue -
State: closed - Opened by refractalize over 11 years ago
#11 - It turns out there are "architects" who just write docs for a living. not code.
Pull Request -
State: closed - Opened by PaulCampbell over 11 years ago
#10 - Treat callback argument specially
Issue -
State: closed - Opened by refractalize over 11 years ago
- 5 comments
#9 - 09 is generated as 0
Issue -
State: closed - Opened by refractalize over 11 years ago
#8 - async return doesn't call callback
Issue -
State: closed - Opened by refractalize over 11 years ago
#7 - Array getAt compilation fails with variable
Issue -
State: closed - Opened by sphvn over 11 years ago
- 3 comments
#6 - async return on if statements
Issue -
State: closed - Opened by refractalize over 11 years ago
#5 - Passing async blocks to non-async functions gets weird
Issue -
State: closed - Opened by refractalize over 11 years ago
#4 - scoped assignments aren't recognised as async
Issue -
State: closed - Opened by refractalize over 11 years ago
#3 - Interpolated strings are not in parens
Issue -
State: closed - Opened by refractalize over 11 years ago
#2 - async is not detected if control structure is async
Issue -
State: closed - Opened by refractalize over 11 years ago
#1 - added npm main pointing at index.js, so require('pogo') works
Pull Request -
State: closed - Opened by joshski over 11 years ago