Change Details

==User story: As a VE user, given there's no reference in the article when I add a basic reference in VE and I use the sub-menu in the reuse dialog to add a sub-reference for that reference then I can create a new sub-reference that's referring the main content of the former ==Acceptance criteria: GIVEN An empty article WHEN I add a basic reference with content `Miller` AND I add a sub-ref reusing the former with the content `page 1` AND save the page THEN a basic reference with an auto-generated name is added AND a new sub-ref with the same name ``` <ref name=":0">Miller</ref> <ref name=":0" details="page 1" /> ``` ==Notes: - This should also work when there's already a reference that's not named yet. ==Dev notes: `ve.dm.MWReferenceNode.static.toDomElements` is responsible for generating the auto name for the converted output but does not save it in the data structure. We need to implement a mechanism that allows the sub-ref to - Get the generated name from the main ref - Independent of if the main ref is rendered after the sub-ref or before A solution to that could be generating auto names early on and saving them in the data structure of the nodes.

==User story: As a VE user I want to add details to an existing reference (creating a subref via the reuse dialog). ==Acceptance criteria: GIVEN An unnamed main ref: ``` <ref>Miller</ref> ``` WHEN I add a sub-ref with the details `page 1` and save the page THEN the main ref has an auto-generated name AND a there is new sub-ref with the same name: ``` <ref name=":0">Miller</ref> <ref name=":0" details="page 1" /> ``` ==Dev notes: `ve.dm.MWReferenceNode.static.toDomElements` is responsible for generating the auto name for the converted output but does not save it in the data structure. We need to implement a mechanism that allows the sub-ref to - Get the generated name from the main ref - Independent of if the main ref is rendered after the sub-ref or before A solution to that could be generating auto names early on and saving them in the data structure of the nodes.

==User story: As a VE user, given there's no reference in the article when I add a basic reference in VE and I use the sub-menu in the reuse dialog to add a sub-reference for that reference then I can create a new sub-reference that's referring the main content of the former I want to add details to an existing reference (creating a subref via the reuse dialog). ==Acceptance criteria: GIVEN An empty article WHEN I add a basicunnamed main reference with content `Miller`: ``` AND I add a sub-ref reusing the former with the content `page 1`<ref>Miller</ref> AND save the page``` TWHEN a basic referenceI add a sub-ref with an auto-generated name is addedthe details `page 1` and save the page THEN the main ref has an auto-generated name AND a there is new sub-ref with the same name: ``` <ref name=":0">Miller</ref> <ref name=":0" details="page 1" /> ``` ==Notes: - This should also work when there's already a reference that's not named yet. ==Dev notes: `ve.dm.MWReferenceNode.static.toDomElements` is responsible for generating the auto name for the converted output but does not save it in the data structure. We need to implement a mechanism that allows the sub-ref to - Get the generated name from the main ref - Independent of if the main ref is rendered after the sub-ref or before A solution to that could be generating auto names early on and saving them in the data structure of the nodes.