| let foundStuff = false; | |
| let items = document.querySelectorAll('li.notifications-list-item') | |
| items.forEach((item) => { | |
| if(item.querySelector('img.avatar-user[alt="@dependabot-preview[bot]"]') || item.querySelector('img.avatar-user[alt="@dependabot[bot]"]') || item.querySelector('img.avatar-user[alt="@renovate[bot]"]')) { | |
| console.log('did find one'); | |
| foundStuff = true; | |
| item.querySelector('input[type="checkbox"]').click(); | |
| } | |
| }); |
MOVED TO https://github.com/CodeMouse92/DEVModInACan
All articles on #beginners should be written for those new to programming, development, networking, or to a particular language. These posts should also require little to no prerequisite knowledge. If you wish, you may rewrite your post to meet these requirements, at which point you may request that the tag be added back. Otherwise, just use the appropriate technology tags. (Read more about the tag rules here.)
Ember has been around since 2011. It's also not the product it was in 2011, and has adapted/evolved into an experienced, dependable ecosystem.
"Safety of the Herd" (article) illustrates that we get to solve more interesting problems when the entire community adheres to a shared set of standards.
"How to learn EmberJS in a hurry" (article) illustrates that the Ember learning curve may not be as steep as you think.
Ember's testing story is superb, and the core team demonstrated the wisdom that comes only through experience, by making it a core feature that is equally as important as the framework itself.
Accessibility- the ember-a11y community and growing collection of addons demonstrates the commitment to the idea that people of all abilities should be able to use the web
| { | |
| /** | |
| * Tell JSHint about global variables. | |
| */ | |
| "predef": [ | |
| // https://github.com/pivotal/jasmine | |
| "after", | |
| "afterEach", |
This plugin got promoted to its own repository.
| // Try to be as sensible as possible about parsing durations | |
| function parseDuration(duration) { | |
| // .75 | |
| if (match = /^\.\d+$/.exec(duration)) { | |
| return parseFloat("0" + match[0]) * 3600; | |
| // 4 or 11.75 | |
| } else if (match = /^\d+(?:\.\d+)?$/.exec(duration)) { | |
| return parseFloat(match[0]) * 3600; | |
| // 01:34 | |
| } else if (match = /^(\d+):(\d+)$/.exec(duration)) { |
Update 2022: git checkout -p <other-branch> is basically a shortcut for all this.
FYI This was written in 2010, though I guess people still find it useful at least as of 2021. I haven't had to do it ever again, so if it goes out of date I probably won't know.
Example: You have a branch refactor that is quite different from master. You can't merge all of the
commits, or even every hunk in any single commit or master will break, but you have made a lot of
improvements there that you would like to bring over to master.
Note: This will not preserve the original change authors. Only use if necessary, or if you don't mind losing that information, or if you are only merging your own work.
