quillblue commented on code in PR #295:
URL: https://github.com/apache/echarts-doc/pull/295#discussion_r1002719170


##########
en/option/partial/group-id.md:
##########
@@ -3,15 +3,59 @@
 
 ## dataGroupId(string)
 
-A groupID common to all data in the series. the groupID will be used to 
classify the data and determine how merge and split animations are performed in 
the universal transition animation.
-
-If you are using the [dataset](~dataset) component to represent the data, it 
is recommended to use `encode.itemGroupID` to specify which dimension is 
encoded as the groupID.
+A group ID assigned to all data items in the series.
 
+This option has a lower priority than `groupId`, which means when `groupId` is 
specified for a certain data item the `dataGroupId` will be simply ignored for 
that data item. For more information, please see `series.data.groupId`.
 
 
 {{ target: partial-data-group-id }}
 
 #${prefix} groupId(string)
 
-The groupID of this data item. groupID will be used to classify the data.
+The group ID of a data item. When `universalTransition` is enabled, the data 
items from the old option and those from the new one, if sharing a same group 
ID, will then be matched and applied to a proper animation after `setOption` is 
called.
+
+If a data item is not specified with a `groupId`, Echarts will try to use 
`series.dataGroupId` as the group ID for the data item. If `series.dataGroupId` 
is not specified either, Echarts will fall back to using the data item's ID as 
its group ID.
+
+If you are using the [dataset](~dataset) component to represent data, you are 
recommended to use `encode.itemGroupId` to specify the dimension that is to be 
encoded as the group ID.
+
+
+{{ target: partial-data-child-group-id }}
+
+#${prefix} childGroupId(string)
+
+The group ID of the child data of a data item. This option is introduced to 
make multiple levels drilldown and aggregation animation possilbe.
+
+~[700x300](${galleryViewPath}doc-example/bar-drilldown&edit=1&reset=1)
+
+Before `childGroupId` is introduced, developers actually can use `groupId` to 
make drilldown and aggregation animation already, but with the limit on the 
times that a continious drilldown or aggregation can happen, which is only one 
time.
+
+`childGroupId`, together with `groupId`, help to form "father-child" 
relationships between data items of different options, such as:

Review Comment:
   it would be better using `parent-child relationships`



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@echarts.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@echarts.apache.org
For additional commands, e-mail: commits-h...@echarts.apache.org

Reply via email to