lbenie/angular-elastic-grid

Wrapper of jquery-elastic-grid for angular 1.x https://github.com/vukhanhtruong/jquery-elastic-grid

Hi 👋🏾

My name is Lucien, and I'm a Senior Software Developer @Shopify

I am a guy who just loves coding and learning new stuff about the web

Frontend technologies I worked with

• React
• Angular
• Vue
• Web Components

I am currently working on Shopify's admin portal.

P.S. I love a11y too!

---

Find me around the web 🌎:

• Personal website lbenie.xyz
• Network with me on LinkedIn 💼

angular-elastic-grid's Issues

An in-range update of karma-sinon-chai is breaking the build 🚨

Version 1.3.0 of karma-sinon-chai just got published.

Branch	Build failing 🚨
Dependency	karma-sinon-chai
Current Version	1.2.4
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As karma-sinon-chai is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 2 commits .

• 1d15460 1.3.0
• bca7e7a chore(deps): bump dependencies to latest versions (#44)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of mocha is breaking the build 🚨

Version 3.3.0 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.2.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/lbenie/angular-elastic-grid/builds/225141283)

---

Release Notes

coverave

Thanks to all our contributors, maintainers, sponsors, and users! ❤️

As highlights:

• We've got coverage now!
• Testing is looking less flaky \o/.
• No more nitpicking about "mocha.js" build on PRs.

🎉 Enhancements

• #2659: Adds support for loading reporter from an absolute or relative path (@sul4bh)
• #2769: Support --inspect-brk on command-line (@igwejk)

🐛 Fixes

• #2662: Replace unicode chars w/ hex codes in HTML reporter (@rotemdan)

🔍 Coverage

• #2672: Add coverage for node tests (@c089, @Munter)
• #2680: Increase tests coverage for base reporter (@epallerols)
• #2690: Increase tests coverage for doc reporter (@craigtaub)
• #2701: Increase tests coverage for landing, min, tap and list reporters (@craigtaub)
• #2691: Increase tests coverage for spec + dot reporters (@craigtaub)
• #2698: Increase tests coverage for xunit reporter (@craigtaub)
• #2699: Increase tests coverage for json-stream, markdown and progress reporters (@craigtaub)
• #2703: Cover .some() function in utils.js with tests (@seppevs)
• #2773: Add tests for loading reporters w/ relative/absolute paths (@sul4bh)

🔩 Other

• Remove bin/.eslintrc; ensure execs are linted (@boneskull)
• #2542: Expand CONTRIBUTING.md (@boneskull)
• #2660: Double timeouts on integration tests (@Munter)
• #2653: Update copyright year ([@Scottkao85], @Munter)
• #2621: Update dependencies to enable Greenkeeper (@boneskull, @greenkeeper)
• #2625: Use trusty container in travis-ci; use "artifacts" addon (@boneskull)
• #2670: doc(CONTRIBUTING): fix link to org members (@coderbyheart)
• Add Mocha propaganda to README.md (@boneskull)
• #2470: Avoid test flake in "delay" test (@boneskull)
• #2675: Limit browser concurrency on sauce (@boneskull)
• #2669: Use temporary test-only build of mocha.js for browsers tests (@Munter)
• Fix "projects" link in README.md (@boneskull)
• #2678: Chore(Saucelabs): test on IE9, IE10 and IE11 (@coderbyheart)
• #2648: Use semistandard directly (@kt3k)
• #2727: Make the build reproducible (@lamby)

Commits

The new version differs by 89 commits0.

• fb1687e :ship: Release v3.3.0
• 1943e02 Add Changelog for v3.3.0
• 861e968 Refactor literal play-icon hex code to a var
• 1d3c5bc Fix typo in karma.conf.js
• 9bd9389 Fix spec paths in test HTML files
• 0a93024 Adds tests for loading reporters w/ relative/absolute paths (#2773)
• 73929ad Comment special treatment of '+' in URL query parsing
• e2c9514 Merge pull request #2769 from igwejk/support_inspect_break_in_opts
• 038c636 Support --inspect-brk on command-line
• b4ebabd Merge pull request #2727 from lamby/reproducible-build
• 882347b Please make the build reproducible.
• a2fc76c Merge pull request #2703 from seppevs/cover_utils_some_fn_with_tests
• ed61cd0 cover .some() function in utils.js with tests
• f42cbf4 Merge pull request #2701 from craigtaub/landingSpec
• 6065242 use stubbed symbol

There are 89 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

angular-elastic grid not able to implement button click

@lbenie great work!

I try to used directive according the step given by you, but not getting success to implement. Can you give demo how to implement click event on button list, I want to add button in button_list and on click call function from the controller.

Thanks