block locators do, but I thought we were just persisting the usage_id not
the whole block usage locator.


On Tue, Sep 3, 2013 at 9:45 AM, Calen Pennington
<notifications@github.com>wrote:

> In cms/djangoapps/contentstore/tests/test_crud.py:
>
> > @@ -226,10 +226,7 @@ def load_from_json(json_data, system, default_class=None, parent_xblock=None):
> >
> >          new_block = system.xblock_from_json(class_, usage_id, json_data)
> >          if parent_xblock is not None:
> > -            children = parent_xblock.children
> > -            children.append(new_block)
> > -            # trigger setter method by using top level field access
> > -            parent_xblock.children = children
> > +            parent_xblock.children.append(new_block.scope_ids.usage_id)
>
> I thought that block locators allowed for pointers across structures.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/edx/edx-platform/pull/839/files#r6125662>
> .
>