Error: [mobx-state-tree] Failed to resolve reference XXX to type 'User'





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







3















Context



I have a React application that is backed by mobx-state-tree (MST). One of the pages makes two parallel API calls to fetch a list of Projects and a list of system Users.



The responses of these two APIs are then applied as snapshot to two sibling nodes in the same tree. The Project model's owner field refers to a User model.



My problem is that the GET project API call often completes earlier than the GET Users API call. Classic "race condition". So, when MST tries to dereference an owner value, the user with such identifier is not available in the tree and I'm getting a run time error like this:




Error: [mobx-state-tree] Failed to resolve reference 'dtGNbVdNOQIAX0OMGaH2r2oSEf2cMSk9AJzPAf4n7kA' to type 'User' (from node: /projectListStore/projects/0/owner)




Question



How do I work around the error?



Please notice that making the API calls depend on each other (await or users.load().then(users => { projects.load(); }) are not an option for our project.



MST Models



export const ProjectModel = types
.model('Project', {
projectId: types.optional(types.identifierNumber, 0),
title: '',
descriptionStatus: '',
projectStatus: '',
startDate: CustomDate,
endDate: CustomDate,
owner: types.maybeNull(types.reference(User)), // -----
})
// ... |
|
export const User = types |
.model('User', { /
userId: types.identifier, // <<<--
userName: '',
firstName: '',
lastName: '',
email: '',
lastVisited: CustomDate,
})
// ...


API example



GET https://service.com/api/users



[
{
"userId": "g-gqpB1EbTi9XGZOf3IkBpxSjpAHM8fpkeL4YZslEL8",
"userName": "john.doe@service.com",
"firstName": "John",
"lastName": "Doe",
"email": "john.doe@service.com",
"lastVisited": "2018-01-18T17:32:48.947"
},
{
...
},
...
]




GET https://service.com/api/workmanagement/projects?minStartDate=&maxStartDate=2018-11-24&status=Active



[
{
"projectId": 1,
"title": "Project Title",
"description": "Praesent luctus vitae nunc sed condimentum. Duis maximus arcu tortor, vitae placerat enim ultrices sed. Etiam scelerisque gravida justo, vitae venenatis dui pellentesque eu.",
"projectStatus": "active",
"startDate": "2018-08-20T00:00:00",
"endDate": "2019-07-01T00:00:00",
"owner": "g-gqpB1EbTi9XGZOf3IkBpxSjpAHM8fpkeL4YZslEL8",
},
{
// ...
},
...
]









share|improve this question































    3















    Context



    I have a React application that is backed by mobx-state-tree (MST). One of the pages makes two parallel API calls to fetch a list of Projects and a list of system Users.



    The responses of these two APIs are then applied as snapshot to two sibling nodes in the same tree. The Project model's owner field refers to a User model.



    My problem is that the GET project API call often completes earlier than the GET Users API call. Classic "race condition". So, when MST tries to dereference an owner value, the user with such identifier is not available in the tree and I'm getting a run time error like this:




    Error: [mobx-state-tree] Failed to resolve reference 'dtGNbVdNOQIAX0OMGaH2r2oSEf2cMSk9AJzPAf4n7kA' to type 'User' (from node: /projectListStore/projects/0/owner)




    Question



    How do I work around the error?



    Please notice that making the API calls depend on each other (await or users.load().then(users => { projects.load(); }) are not an option for our project.



    MST Models



    export const ProjectModel = types
    .model('Project', {
    projectId: types.optional(types.identifierNumber, 0),
    title: '',
    descriptionStatus: '',
    projectStatus: '',
    startDate: CustomDate,
    endDate: CustomDate,
    owner: types.maybeNull(types.reference(User)), // -----
    })
    // ... |
    |
    export const User = types |
    .model('User', { /
    userId: types.identifier, // <<<--
    userName: '',
    firstName: '',
    lastName: '',
    email: '',
    lastVisited: CustomDate,
    })
    // ...


    API example



    GET https://service.com/api/users



    [
    {
    "userId": "g-gqpB1EbTi9XGZOf3IkBpxSjpAHM8fpkeL4YZslEL8",
    "userName": "john.doe@service.com",
    "firstName": "John",
    "lastName": "Doe",
    "email": "john.doe@service.com",
    "lastVisited": "2018-01-18T17:32:48.947"
    },
    {
    ...
    },
    ...
    ]




    GET https://service.com/api/workmanagement/projects?minStartDate=&maxStartDate=2018-11-24&status=Active



    [
    {
    "projectId": 1,
    "title": "Project Title",
    "description": "Praesent luctus vitae nunc sed condimentum. Duis maximus arcu tortor, vitae placerat enim ultrices sed. Etiam scelerisque gravida justo, vitae venenatis dui pellentesque eu.",
    "projectStatus": "active",
    "startDate": "2018-08-20T00:00:00",
    "endDate": "2019-07-01T00:00:00",
    "owner": "g-gqpB1EbTi9XGZOf3IkBpxSjpAHM8fpkeL4YZslEL8",
    },
    {
    // ...
    },
    ...
    ]









    share|improve this question



























      3












      3








      3


      1






      Context



      I have a React application that is backed by mobx-state-tree (MST). One of the pages makes two parallel API calls to fetch a list of Projects and a list of system Users.



      The responses of these two APIs are then applied as snapshot to two sibling nodes in the same tree. The Project model's owner field refers to a User model.



      My problem is that the GET project API call often completes earlier than the GET Users API call. Classic "race condition". So, when MST tries to dereference an owner value, the user with such identifier is not available in the tree and I'm getting a run time error like this:




      Error: [mobx-state-tree] Failed to resolve reference 'dtGNbVdNOQIAX0OMGaH2r2oSEf2cMSk9AJzPAf4n7kA' to type 'User' (from node: /projectListStore/projects/0/owner)




      Question



      How do I work around the error?



      Please notice that making the API calls depend on each other (await or users.load().then(users => { projects.load(); }) are not an option for our project.



      MST Models



      export const ProjectModel = types
      .model('Project', {
      projectId: types.optional(types.identifierNumber, 0),
      title: '',
      descriptionStatus: '',
      projectStatus: '',
      startDate: CustomDate,
      endDate: CustomDate,
      owner: types.maybeNull(types.reference(User)), // -----
      })
      // ... |
      |
      export const User = types |
      .model('User', { /
      userId: types.identifier, // <<<--
      userName: '',
      firstName: '',
      lastName: '',
      email: '',
      lastVisited: CustomDate,
      })
      // ...


      API example



      GET https://service.com/api/users



      [
      {
      "userId": "g-gqpB1EbTi9XGZOf3IkBpxSjpAHM8fpkeL4YZslEL8",
      "userName": "john.doe@service.com",
      "firstName": "John",
      "lastName": "Doe",
      "email": "john.doe@service.com",
      "lastVisited": "2018-01-18T17:32:48.947"
      },
      {
      ...
      },
      ...
      ]




      GET https://service.com/api/workmanagement/projects?minStartDate=&maxStartDate=2018-11-24&status=Active



      [
      {
      "projectId": 1,
      "title": "Project Title",
      "description": "Praesent luctus vitae nunc sed condimentum. Duis maximus arcu tortor, vitae placerat enim ultrices sed. Etiam scelerisque gravida justo, vitae venenatis dui pellentesque eu.",
      "projectStatus": "active",
      "startDate": "2018-08-20T00:00:00",
      "endDate": "2019-07-01T00:00:00",
      "owner": "g-gqpB1EbTi9XGZOf3IkBpxSjpAHM8fpkeL4YZslEL8",
      },
      {
      // ...
      },
      ...
      ]









      share|improve this question
















      Context



      I have a React application that is backed by mobx-state-tree (MST). One of the pages makes two parallel API calls to fetch a list of Projects and a list of system Users.



      The responses of these two APIs are then applied as snapshot to two sibling nodes in the same tree. The Project model's owner field refers to a User model.



      My problem is that the GET project API call often completes earlier than the GET Users API call. Classic "race condition". So, when MST tries to dereference an owner value, the user with such identifier is not available in the tree and I'm getting a run time error like this:




      Error: [mobx-state-tree] Failed to resolve reference 'dtGNbVdNOQIAX0OMGaH2r2oSEf2cMSk9AJzPAf4n7kA' to type 'User' (from node: /projectListStore/projects/0/owner)




      Question



      How do I work around the error?



      Please notice that making the API calls depend on each other (await or users.load().then(users => { projects.load(); }) are not an option for our project.



      MST Models



      export const ProjectModel = types
      .model('Project', {
      projectId: types.optional(types.identifierNumber, 0),
      title: '',
      descriptionStatus: '',
      projectStatus: '',
      startDate: CustomDate,
      endDate: CustomDate,
      owner: types.maybeNull(types.reference(User)), // -----
      })
      // ... |
      |
      export const User = types |
      .model('User', { /
      userId: types.identifier, // <<<--
      userName: '',
      firstName: '',
      lastName: '',
      email: '',
      lastVisited: CustomDate,
      })
      // ...


      API example



      GET https://service.com/api/users



      [
      {
      "userId": "g-gqpB1EbTi9XGZOf3IkBpxSjpAHM8fpkeL4YZslEL8",
      "userName": "john.doe@service.com",
      "firstName": "John",
      "lastName": "Doe",
      "email": "john.doe@service.com",
      "lastVisited": "2018-01-18T17:32:48.947"
      },
      {
      ...
      },
      ...
      ]




      GET https://service.com/api/workmanagement/projects?minStartDate=&maxStartDate=2018-11-24&status=Active



      [
      {
      "projectId": 1,
      "title": "Project Title",
      "description": "Praesent luctus vitae nunc sed condimentum. Duis maximus arcu tortor, vitae placerat enim ultrices sed. Etiam scelerisque gravida justo, vitae venenatis dui pellentesque eu.",
      "projectStatus": "active",
      "startDate": "2018-08-20T00:00:00",
      "endDate": "2019-07-01T00:00:00",
      "owner": "g-gqpB1EbTi9XGZOf3IkBpxSjpAHM8fpkeL4YZslEL8",
      },
      {
      // ...
      },
      ...
      ]






      javascript reactjs mobx mobx-state-tree






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 26 '18 at 5:10







      Igor Soloydenko

















      asked Nov 25 '18 at 3:36









      Igor SoloydenkoIgor Soloydenko

      2,20021949




      2,20021949
























          1 Answer
          1






          active

          oldest

          votes


















          0














          It sounds like you're potentially loading the user data after the project model is created
          It might be as easy as using a late reference. This is meant for, as it sounds, any types that may get created after this model is created.



          instead of this
          owner: types.maybeNull(types.reference(User))



          try this
          owner: types.maybeNull(types.late(() => types.reference(User)))






          share|improve this answer
























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53464439%2ferror-mobx-state-tree-failed-to-resolve-reference-xxx-to-type-user%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            It sounds like you're potentially loading the user data after the project model is created
            It might be as easy as using a late reference. This is meant for, as it sounds, any types that may get created after this model is created.



            instead of this
            owner: types.maybeNull(types.reference(User))



            try this
            owner: types.maybeNull(types.late(() => types.reference(User)))






            share|improve this answer




























              0














              It sounds like you're potentially loading the user data after the project model is created
              It might be as easy as using a late reference. This is meant for, as it sounds, any types that may get created after this model is created.



              instead of this
              owner: types.maybeNull(types.reference(User))



              try this
              owner: types.maybeNull(types.late(() => types.reference(User)))






              share|improve this answer


























                0












                0








                0







                It sounds like you're potentially loading the user data after the project model is created
                It might be as easy as using a late reference. This is meant for, as it sounds, any types that may get created after this model is created.



                instead of this
                owner: types.maybeNull(types.reference(User))



                try this
                owner: types.maybeNull(types.late(() => types.reference(User)))






                share|improve this answer













                It sounds like you're potentially loading the user data after the project model is created
                It might be as easy as using a late reference. This is meant for, as it sounds, any types that may get created after this model is created.



                instead of this
                owner: types.maybeNull(types.reference(User))



                try this
                owner: types.maybeNull(types.late(() => types.reference(User)))







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Mar 15 at 22:44









                HarvolevHarvolev

                563




                563
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53464439%2ferror-mobx-state-tree-failed-to-resolve-reference-xxx-to-type-user%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    這個網誌中的熱門文章

                    Tangent Lines Diagram Along Smooth Curve

                    Yusuf al-Mu'taman ibn Hud

                    Zucchini