Skip to content
Snippets Groups Projects
Commit 8279d3a5 authored by Sean Madsen's avatar Sean Madsen Committed by GitHub
Browse files

Merge pull request #327 from tschuettler/patch-3

Fix broken link
parents 50b0f29d d7d63a35
No related branches found
No related tags found
No related merge requests found
...@@ -101,7 +101,7 @@ function _civicrm_api3_tag_create_spec(&$params) { ...@@ -101,7 +101,7 @@ function _civicrm_api3_tag_create_spec(&$params) {
} }
``` ```
If the `_spec` function makes no alterations to `$params`, then each field will behave as defined in the [schema definition](framework/schema-definition/#table-field) for the entity. All of those field-level xml schema tags are also available for use in the API `_spec` function. So for example, you can use `$params['id']['type'] = CRM_Utils_Type::T_INT;` to specify that the `'id'` field must be an integer. If the `_spec` function makes no alterations to `$params`, then each field will behave as defined in the [schema definition](/framework/database/schema-definition.md#table-field) for the entity. All of those field-level xml schema tags are also available for use in the API `_spec` function. So for example, you can use `$params['id']['type'] = CRM_Utils_Type::T_INT;` to specify that the `'id'` field must be an integer.
Additionally, the following settings may be applied to each field: Additionally, the following settings may be applied to each field:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment