brianmriley

// The following is a configuration example to lazy load translations. It's meant to provide specificity and clarity to 
// anyone still wondering how it all fits together, I have the following setup (using abbreviated module definitions):

////////////////////////////////////////////////////////////////////////////////////////////////////////////
// AppModule
////////////////////////////////////////////////////////////////////////////////////////////////////////////


// AoT requires an exported function for factories.
export function HttpLoaderFactory(http: HttpClient): TranslateHttpLoader {

brianmriley

echo '' | openssl s_client -connect www.okta.com:443

brianmriley

// Taken from SO: https://stackoverflow.com/questions/47119426/how-to-set-file-objects-and-length-property-at-filelist-object-where-the-files-a

const dT = new ClipboardEvent('').clipboardData || // Firefox < 62 workaround exploiting https://bugzilla.mozilla.org/show_bug.cgi?id=1422655
  new DataTransfer(); // specs compliant (as of March 2018 only Chrome)
dT.items.add(new File(['foo'], 'programmatically_created.txt'));
inp.files = dT.files;

brianmriley

describe("Foo constructor", function() {
  it("should call its `bar()` instance method.", function() {
      spyOn(Foo.prototype, 'bar');
      var foo = new Foo();
      expect(Foo.prototype.bar).toHaveBeenCalled();
  });
});

brianmriley

// grep {searchString} {targetFile} > {outputFile}
grep "loadChunk(" mysxm.log > mysxm-load-chunk.log

brianmriley

#######################
# Chrome
alias chrome="open /Applications/Google\ Chrome.app/"
alias chromedev="open /Applications/Google\ Chrome.app/ --args --ignore-certificate-errors --allow-running-insecure-content --reduce-security-for-testing --disable-web-security --unsafely-treat-insecure-origin-as-secure=http://local-dev.siriusxm.com:8890 --user-data-dir=~/Library/Application Support/Google/Chrome/Default"
#######################

brianmriley

// I've created a simple logger (wraps console.* methods) that provides output similar to say Log4J or other robust 
// loggers out there for the enterprise, but a huge missing piece (for me) is that you can no longer see the file 
// reference and line number from the client object using the logger. When you use console.log() OOTB it'll spit out 
// a clickable link to the file and line number that executed the console.log making it easy to debug; when you wrap 
// console.log it simply spits out the logger file reference and the line number the console.log was executed, so 
// all logging shows up as from the logger wrapper (which is technically correct)...bottom line, you lose the context 
// from which you actually made the logging call and I'd like to get that back.

// Aside from blackboxing, is there another way to wrap console.log() such that it binds to the client callee
// and ultimately shows the correct file reference and line number of the callee (and not the log wrapper)?

brianmriley

1) Open repo in tower.
2) Right-click on remotes/origin in left pane.
3) Select `Edit Connection Settings`.

brianmriley

var urlList = model.getURLs();

var loadAndParse = function (url)
{
	// both load() and parse() are promise based functions
	return load(url).then(parse);
};

/**
 * Allows for the sequentially calling of promise based functions by iterating over a list of

brianmriley

// pulled from SO http://stackoverflow.com/questions/6393943/convert-javascript-string-in-dot-notation-into-an-object-reference
// NOTE: Array.reduce() may not be available in older browsers

function index(obj,i) {return obj[i]}
'a.b.etc'.split('.').reduce(index, obj);

var obj = {a:{b:{etc:5}}};

index(obj,'a.b.etc');