Thank you very much for the responses. It turned out in my case that the exception was from another call (the url for 'properties' call was correct), however I found the attribute "url_with_id", which solved the problem, I'd assume it is the right way to construct object specific url.
On Mon, Feb 10, 2020 at 11:23 PM Ashesh Vashi <ashesh.va...@enterprisedb.com> wrote: > On Tue, Feb 11, 2020 at 10:49 AM Khushboo Vashi < > khushboo.va...@enterprisedb.com> wrote: > >> Hi, >> >> On Mon, Feb 10, 2020 at 11:13 PM Radoslaw Garbacz < >> radoslaw.garb...@xtremedatainc.com> wrote: >> >>> Hi, >>> >>> I am just getting familiar with the sources. >>> >>> As the title, when requesting node's properties the call to >>> "generate_url" has explicit "with_id=false" (node.js line 287 in "getView" >>> function), which results in the generated url not to have this node's ID >>> (just it's parent). >>> >>> What is the purpose of 'properties' on a node request, shouldn't it have >>> its ID? >>> >> ID is required to fetch the properties of any object. >> In this particular scenario, we have set the urlRoot property of the >> backbone model, so when we fetch the data, backbone will append the id to >> the urlRoot if it's available in the model. >> > We've used that for listing the properties of the objects of same/related > type in the properties tab for any collection node (i.e. Databases, > Schemas, Tables, Roles, and many more) > > -- Thanks, Ashesh > >> >> Ref: https://backbonejs.org/#Model-urlRoot >> >> Thanks, >> Khushboo >> >>> Would greatly appreciate some details regarding this issue. >>> >>> -- >>> Best Regards, >>> >>> Radoslaw Garbacz >>> XtremeData Incorporated >>> >> -- Best Regards, Radoslaw Garbacz XtremeData Incorporated
