From 5c1a02ab2f907a382fdc7dbab92632d46f83145a Mon Sep 17 00:00:00 2001
From: tschuettler <tschuettler@oxfam.de>
Date: Mon, 4 Sep 2017 12:34:51 +0200
Subject: [PATCH] Fix broken link
---
docs/framework/api-architecture.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/framework/api-architecture.md b/docs/framework/api-architecture.md
index b3f785d6..54b2885f 100644
--- a/docs/framework/api-architecture.md
+++ b/docs/framework/api-architecture.md
@@ -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/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.
Additionally, the following settings may be applied to each field:
--
GitLab