Why is the digitalocean_project backwards when assigning resources to projects?

[CheatCodeSam]

Hello, I'm a little confused as to why the API was written where child resources are included in the project resource, instead of child resources have a reference to their parents. Doesn't this seem to be more intuitive?

resource "digitalocean_droplet" "foobar" {
  name   = "example"
  size   = "s-1vcpu-1gb"
  image  = "ubuntu-22-04-x64"
  region = "nyc3"
  project = digitalocean_project.playground.id
}

resource "digitalocean_project" "playground" {
  name        = "playground"
  description = "A project to represent development resources."
  purpose     = "Web Application"
  environment = "Development"
}

[danaelhe]

Thank you so much for this write up. You're right, your suggested approach is more intuitive. I've relayed your feedback to the appropriate product manager for the underlying API. Will give an update as soon as I have one. Thank you for the feedback!

[CheatCodeSam]

I would be willing to contribute to this.

[danaelhe]

Appreciate your willingness to contribute! I suppose we could fake it in terraform...to assign a resource to a project via /v2/projects/$PROJECT_ID/resources rather than specifying the project as an attribute of the resource, I think we'd need to make API requests to the projects endpoint for every single resource in a config.