this looks good to me - was there more work to do here?
I would also look on the AVP side here - because of the rename I think there might be issues both in CoGs and AVP.

Please check all these issues and maybe write tests: (sorry I did not think of these issues at grooming)

• when AVP associates a nodeView with a node it uses various names, check for instance if the list create node still attaches the correct view when uploaded.
• CoGS has a list of aliased names for dynamo nodes, list.create may be one of these - the name in cogs might need to change or grow to include both names - @gregmarr will know more.

@mjkkirschner @gregmarr I looked into the repercussions of the renaming and all 3 node now return null on the AVP CoGS route but appear with the proper nodeView. It also seems Function.Apply and Function.Compose never functioned as expected and always returned null even prior to the renaming.

@alfarok CoGS /TS does not handle function passing so that makes sense for apply and compose.

@mjkkirschner I tried updating List.Create in AVP in the NodeFactory.ts mapping file and it didn't seem to influence anything. List.Create works without any changes and even with the changes is still showing up with the dot naming. Also not sure if this is expected but all the objects are nested an additional level from what is produced in Dynamo. Since the AC doesn't include the AVP work I am going to merge this and file another task to take a closer look if that is okay?