Front-end work for duplicating components on the unit page.

[cahrens]

@singingwolfboy and @andy-armstrong Please review.

@marcotuts Please check out my CSS changes.

STUD-1186

[cahrens]

postJSON is defined in main.coffee. We always load that when running CMS, but we don't always load it when running unit tests (unless an earlier test loads it). I'm making the dependency more clearly stated.

[andy-armstrong]

👍 Looks great, and those are awesome tests.

[marcotuts]

I've branched off of this to add the visual styling changes for the component header, and should have something to review later today. I was planning on merging my branch into this one prior to merge of christina/duplicate into master, letting the work enter master as 1 PR.

If anybody feels I should instead treat the visual styling as a separate changelog item then I can open a pull request to master after this branch (as is) merges.

[cahrens]

@marcotuts I would prefer to merge this PR first if it is ready to go. I'm still waiting on @singingwolfboy, as well as a thumbs-up from you. So I think it comes down to timing more than a philosophical stance.

[singingwolfboy]

Instead of making the lettuce test use the zero-based index (awkward phrasing), can we use the terms "first", "second", "third", and so on? For example:

@step(u'I duplicate the (first|second|third) component$')
def duplicated_component(step, ordinal):
    ord_map = {
        "first": 0,
        "second": 1,
        "third": 2,
    }
    index = ord_map[ordinal]
    # and continue

[cahrens]

I could, but I thought it was overkill (and not very extensible, as the mapping has to exist for each ordinal). Let me think about it.

[singingwolfboy]

What happens if this call is unsuccessful?

[cahrens]

The "Adding" or "Duplicating" notification is replaced by our standard "Studio is having trouble saving your work" message at the bottom. I don't add the component into the unit, under the assumption that the error meant the creation or duplication did not work.

In reality, it is possible that the creation or duplication did work, and the error occurred after that. In that case, refreshing the page (which we recommend in the error message) will show the component.

The code as previously written always assumed that the operation was successful-- the component was added to the page immediately, and the analytics tracking message was created, both before we even heard back from the server.

[singingwolfboy]

Why not do:

gettext('Adding') + '…'

[singingwolfboy]

Ugh, nevermind. I don't know which is correct.

[singingwolfboy]

👍