This information source from the following url:
http://peter.sh/experiments/chromium-command-line-switches/
And also in the chromium source:
https://source.chromium.org/chromium/chromium/src/+/main:media/base/media_switches.cc
package com.leviwilson.test; | |
import static org.hamcrest.CoreMatchers.is; | |
import static org.hamcrest.CoreMatchers.not; | |
import static org.junit.Assert.assertThat; | |
import java.util.Date; | |
import org.junit.Test; |
// Needed in AndroidManifest: | |
<!-- Permission for using NFC hardware --> | |
<uses-permission android:name="android.permission.NFC"/> | |
<!-- Forcing device to have NFC hardware --> | |
<uses-feature android:name="android.hardware.nfc" android:required="true"/> | |
<!-- Registering app for receiving NFC's TAG_DISCOVERED intent --> | |
<intent-filter> | |
<action android:name="android.nfc.action.TAG_DISCOVERED"/> | |
<category android:name="android.intent.category.DEFAULT"/> | |
</intent-filter> |
This information source from the following url:
http://peter.sh/experiments/chromium-command-line-switches/
And also in the chromium source:
https://source.chromium.org/chromium/chromium/src/+/main:media/base/media_switches.cc
# delete local tag '12345' | |
git tag -d 12345 | |
# delete remote tag '12345' (eg, GitHub version too) | |
git push origin :refs/tags/12345 | |
# alternative approach | |
git push --delete origin tagName | |
git tag -d tagName |
wiredep = require( 'wiredep' ) | |
path = require 'path' | |
# Karma configuration | |
module.exports = ( config ) -> | |
config.set | |
# enable / disable watching file and executing tests whenever any file changes | |
autoWatch: true | |
# base path, that will be used to resolve files relative to this file |
Sure, Github wins on the UI. Hands down. But, despite my initial annoyance with Gerrit when I first started using it almost a year ago, I am now a convert. Fully. Let me tell you why.
Note: This is an opinionated (on purpose) piece. I assume your preferences are like mine on certain ideas, such as:
The documentation for Gerrit when it comes to formatting comments is quite lacking. Here is short list created by trial and error and looking at the source code in: | |
./gerrit-gwtexpui/src/main/java/com/google/gwtexpui/safehtml/client/SafeHtml.java | |
Lists: | |
* List item 1 | |
* List item 2 | |
- List item 1 | |
- List item 2 |
After scouring the internet and piece-mealing together the correct way to do this, here is a step-by-step, all-in-one-place guide to making logback STFU when running your unit tests.
Save the following as logback-test.xml
under src/test/resources
:
<configuration>
<appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender">
<encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder">
<pattern>%msg%n</pattern>
// before load polyfill.js | |
<script> | |
// black list scroll event handler for addEventListener | |
Zone[Zone.__symbol__('BLACK_LISTED_EVENTS')] = ['scroll', 'mouseenter', 'mouseleave', 'mousemove', 'mouseover', 'mouseout', 'mousewheel']; | |
// black list scroll event handler for onProp | |
const targets = [window, Document.prototype, HTMLBodyElement.prototype, HTMLElement.prototype]; | |
__Zone_ignore_on_properties = []; | |
targets.forEach(function(target) { | |
__Zone_ignore_on_properties.push({ |
Photo by Ricardo Gomez Angel on Unsplash
This gist is a collection of common patterns I've personally used here and there with Custom Elements.
These patterns are all basic suggestions that could be improved, enriched, readapted, accordingly with your needs.