Michael Peirce

Ember assert is not correctly transformed when using optional chaining

3

If I start with this code ``` import { assert } from '@ember/debug'; const foo = { bar: { baz: 'something' } }; assert('baz', foo.bar?.baz); ``` it gets transformed into...

Fix keeping time through tz to correctly handle being near DST boundaries

2

This is a fix for https://github.com/moment/moment-timezone/issues/871 This change simplifies the process by just using `moment.tz(this.toArray(), name)`, so that it doesn't have to deal with offsets directly. I then also added...

.tz(.., true) incorrect around DST

3

Fiddle: https://jsfiddle.net/r3qx7zh9/2/ ``` const utc = moment.utc('2018-03-11T04:00'); const converted = utc.tz('America/Los_Angeles', true); console.log(converted.toString()); console.log(converted.toISOString(true)); const direct = moment.tz('2018-03-11T04:00', 'America/Los_Angeles'); console.log(direct.toString()); console.log(direct.toISOString(true)); ``` Output: ``` "Sun Mar 11 2018 05:00:00 GMT-0700"...

When you have a `hasMany` property, and define another property using as follows: ``` people: hasMany(Thing, { key: 'thing_ids' }), peopleNames: Ember.computed.mapBy('people', 'name'), ``` then `peopleNames` will not update correctly...

Currently, if you try to export something named `I18n`, the `filenames/match-exported` rule will enforce that the file name should be `i-18n`, which is not desired. It would be best to...

There are plenty of cases, especially when writing tests, where it makes more sense to use `defer` than to do something like ``` let resolvePromise; let promise = new Promise(resolve...