Question - Support for multi-level resources?

[atul-nagar]

Hello,
I'm trying to create a multi-level heirarchy of resources, but am unable to get it to work beyond two top level resources. Below is the schema definition:

var Foundation = schema.Schema{
	Description: "Schema describing foundation",
	Fields: schema.Fields{
		"id": schema.IDField,
		"name": {
			Required:   true,
			Filterable: true,
			Sortable:   true,
			Validator:  &schema.String{},
		},
	},
}

var Org = schema.Schema{
	Description: "Schema describing Org",
	Fields: schema.Fields{
		"id": schema.IDField,
		"name": {
			Required:   true,
			Filterable: true,
			Sortable:   true,
			Validator:  &schema.String{},
		},
		"foundation": {
			Required:   true,
			Filterable: true,
			Sortable:   true,
			Validator: &schema.Reference{
				Path: "foundations",
			},
		},
	},
}

var Space = schema.Schema{
	Description: "Schema describing Space",
	Fields: schema.Fields{
		"id": schema.IDField,
		"name": {
			Required:   true,
			Filterable: true,
			Sortable:   true,
			Validator:  &schema.String{},
		},
		"org": {
			Required:   true,
			Filterable: true,
			Sortable:   true,
			Validator: &schema.Reference{
				Path: "orgs",
			},
		},
	},
}

And the corresponding binding:

foundations := index.Bind("foundations", fractal_schema.Foundation, mem.NewHandler(), resource.Conf{
		AllowedModes: resource.ReadWrite,
	})

	orgs := foundations.Bind("orgs", "foundation", fractal_schema.Org, mem.NewHandler(), resource.Conf{
		AllowedModes: resource.ReadWrite,
	})

	spaces := orgs.Bind("spaces", "org", fractal_schema.Space, mem.NewHandler(), resource.Conf{
		AllowedModes: resource.ReadWrite,
	})

This gives me the following error:
{"time":"2017-09-28T14:59:34+05:30","level":"fatal","message":"Invalid API configuration: foundations.orgs.spaces: schema compilation error: org: can't find resource 'orgs'"}
exit status 1

Any tips would be helpful.
Thanks

[smyrman]

Path: "orgs",

should be:

Path: "foundations.orgs",

[atul-nagar]

thanks, does it also have an impact on how one invokes a POST operation on the leaf resource?
e.g.

POST  http://localhost:8080/api/foundations/<foundationid>/orgs/<orgid>/spaces
content-type: application/json

{
    "name": "space1"
}

fails with an error

HTTP/1.1 422 Unprocessable Entity
Content-Type: application/json
Request-Id: b76ecieo4oi3792l7opg
Vary: Origin
Date: Thu, 28 Sep 2017 12:08:41 GMT
Content-Length: 93

{
  "code": 422,
  "issues": {
    "foundation": [
      "invalid field"
    ]
  },
  "message": "Document contains error(s)"
}

[smyrman]

This is interesting. It could be a bug, or it could be intended.

I suppose it might work if you add a "foundation" filed to the outer resource, even if it duplicates link information.

[smyrman]

@rs, what is the intended behaviour here?

[atul-nagar]

Adding foundation field to the outer resources might be worth trying, however not what I would ideally want to do.

[rs]

You need to use foundations.orgs as Path and define the foundation field in the space schema.

[rs]

I agree that we should only require the parent object as a field. Please fill a bug report.

[smyrman]

Closing this question now.

[Dragomir-Ivanov]

I wonder if this is related to #231 / #233