Conversation
|
|
||
| 1. If there are attribute-specific CRUD permissions that need to be enforced on a table, those need to be explicitly described in the `attribute_permissions` array. | ||
| 1. If a non-hash attribute is given some level of CRUD access, that same access will be assigned to the table’s `hash_attribute` (also referred to as the `primary_key`), even if it is not explicitly defined in the permissions JSON. | ||
| 1. If a non-hash attribute is given some level of CRUD access, that same access will be assigned to the table's `hash_attribute` (also referred to as the `primary_key`), even if it is not explicitly defined in the permissions JSON. |
There was a problem hiding this comment.
I know markdown renderers will treat duplicate numbers as apart of the same numbered list, but for humans like myself, I kinda makes it less readable.
There was a problem hiding this comment.
shoot, yeah. it's not like ai can't help to fix the order whenever a list is updated anyway. that was the real appeal of keeping them all 1. didn't think to change this since it was just some minor update to an existing list.
know if we use both types of ordered lists in docs so it wouldn't be a big deal if I fix this one?
| 1. If a non-hash attribute is given some level of CRUD access, that same access will be assigned to the table's `hash_attribute` (also referred to as the `primary_key`), even if it is not explicitly defined in the permissions JSON. | ||
|
|
||
| _See table_name1’s permission set for an example of this – even though the table’s hash attribute is not specifically defined in the attribute_permissions array, because the role has CRUD access to ‘attribute1’, the role will have the same access to the table’s hash attribute._ | ||
| _See table_name1's permission set for an example of this – even though the table's hash attribute is not specifically defined in the attribute_permissions array, because the role has CRUD access to 'attribute1', the role will have the same access to the table's hash attribute._ |
There was a problem hiding this comment.
Maybe help point people to table_name1?
| _See table_name1's permission set for an example of this – even though the table's hash attribute is not specifically defined in the attribute_permissions array, because the role has CRUD access to 'attribute1', the role will have the same access to the table's hash attribute._ | |
| _See table_name1's permission set above for an example of this – even though the table's hash attribute is not specifically defined in the attribute_permissions array, because the role has CRUD access to 'attribute1', the role will have the same access to the table's hash attribute._ |
There was a problem hiding this comment.
I'll see if I can do this and a little more...
🚀 Preview DeploymentYour preview deployment is ready! 🔗 Preview URL: https://preview.harper-docs.stage.harperfabric.com/pr-447 This preview will update automatically when you push new commits. |
4 participants
No description provided.