Release 1.2.0

[snewcomer]

close #200 #193

[pichfl]

How would one fix the deprecation introduced in this release? I feel like I'm missing a step here.

[williamweckl]

@pichfl the fixes has already being made. This PR only releases it.

@snewcomer any expectations to release that?

[pichfl]

Hence why I'm asking. Installing this release will result in deprecation warnings without a clear path on how to fix them. The text inside the warning is not helpful for consumers of the add-on.

If I'm wrong, please point me and other people running into the same deprecation into the right direction.

[willviles]

@pichfl is right... the following deprecation warning is confusing. Help appreciated!

DEPRECATION: If you are overriding ember-router-scroll's implementation of "pushState", then you can subclass and override a new location object from: import HistoryLocation from '@ember/routing/history-location'; [deprecation id: ember-router-scroll]

ember-router-scroll/addon/locations/router-scroll.js

Lines 11 to 41 in 695d894

	export default HistoryLocation.extend({
	pushState(path) {
	deprecate(
	`If you are overriding ember-router-scroll's implementation of "pushState", then you can subclass and override a new location object from: import HistoryLocation from '@ember/routing/history-location';`,
	false,
	{
	id: 'ember-router-scroll',
	until: '2.0.0'
	}
	);
	const state = { path, uuid: uuid() };
	get(this, 'history').pushState(state, null, path);
	set(this, '_previousURL', this.getURL());
	},
	replaceState(path) {
	deprecate(
	`If you are overriding ember-router-scroll's implementation of "replaceState", then you can subclass and override a new location object from: import HistoryLocation from '@ember/routing/history-location';`,
	false,
	{
	id: 'ember-router-scroll',
	until: '2.0.0'
	}
	);
	const state = { path, uuid: uuid() };
	get(this, 'history').replaceState(state, null, path);
	set(this, '_previousURL', this.getURL());
	}
	});