approach for maintaining URL params when embedding apps/components

Looks like you need to add change-logging in stripes-core.

w00t!!

As of Friday this issue is complete. I am finishing up linting and tests and will be submitting a PR this afternoon.

The reason STCON-47 is blocking this is that the init method of a LocalResourse is overriding URL data that I am dispatching to the store before a LocalResourse is created. When the page loads and there is query data in the URL, we need the nominated LocalResource to initialize with whatever data is there, instead of the default initial data that is expressed in the manifest. This should work, as there is an attempt within the LocalResource's init method to keep the initial values from being dispatched if there is already data in the redux store for that local resource. BUT because that condition was too permissive, the init method is overriding the data from the URL.

This issue is very close to being wrapped up. Currently a localResource is being used to handle all the state that had previously been kept in the url. I had hoped to get this completed on Friday, but I spun my wheels a little bit with some misguided attempts to update the URL from the LocalResources reducer. After talking with both Mike and Jason about this on Friday, I am now working on handling the updating of the updating of the URL from stripes-core instead of stripes connect.

Once that is done the only thing that will remain is the pre-populating of the nominated localResurce's initial values based on values that are currently in the query string.

I am on track to having this done in the first part of this week.