Reading custom fields.

[holden]

I'm having the same issue as here: https://github.com/orgs/swellstores/discussions/152

But when I tried updating the permissions for my storefront's public key it's still not letting me read it. I'm currently storing the value in the content namespace but I'd like to be able use it in the same way as price and add a few others as well.

I tried this changing the storefront public key permissions like so:

{
  "permissions": {
    "products": {
      "fields": ["price_per_person"]
      }
    }
}

It succeeded but didn't seem to update them, at least not in any way I could see. What am I doing wrong here?

[logeshswell]

If you want to return the field (price_per_person) as normal as price field, then you need to create the field under None API namespace.
Then, granting the read permission like you described in the screenshot should work.

Can you try and confirm if that works?

[holden]

I have a more complicated related question to permissions, what do we do about related collections?

We followed the tutorial here on adding vendors to products https://developers.swell.is/guides/build-a-marketplace.

Now we just want to be able to expose a few fields on the product, eg the name of the vendor, their website, logo etc.

query getProductBySlug {
  productBySlug(slug: "evenchilada-feud") {
    id
    name
    slug
    price
      content {
      brand {
        name
      }
    }
  }
}

But I'm getting a permissions error "message": "This action is not permitted"

How does this work when the permissions are for accounts related to product?

[logeshswell]

If you open up permissions for the accounts model, then all the fields under accounts will be accessible. Otherwise, none of the field will be accessible.

I remember that we recently removed the support to open up permissions for individual fields for the related collections.

[holden]

Ok, I'll try that thanks. Is there anything I should or could do to limit the accounts exposed, eg scoping for an account group? If that were possible, or I suppose I could simply limited the fields I expose, name, description, etc.? instead of making all of the accessible.

[holden]

Last permission question I promise, I tried updating my account permissions on the public key to:

{
  "permissions": {
    "accounts": {
      "fields": [
        "name",
        "content"
      ]
    }
  }
}

Which seemed to work but I'm still getting permission errors, even though it nicely helps autocomplete as I type.

query getProductBySlug {
  productBySlug(slug: "evenchilada-feud") {
    id
    name
    slug
    price
    pricePerPerson
    content {
      brand {
        name
        content {
          websiteUrl
          description
          logo {
            data
          }
        }
      }
    }
  }
}

[holden]

@logeshswell I tried various things but I still cannot seem to get a connected model to work. It clearly see that it's connected correctly, it just doesn't like the permssions: "code": "permission_error",