From 6f7fd11bbf00d37efc7498ea1a38ac53901aa33e Mon Sep 17 00:00:00 2001 From: jnachtigall Date: Thu, 4 Jun 2020 04:18:05 +0200 Subject: [PATCH] Fix dead link for definitely not compliant `enumNames` property (#1752) * Fix dead link for definitely not compliant `enumNames` property * Update single.md Co-authored-by: Ashwin Ramaswami --- docs/usage/single.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/usage/single.md b/docs/usage/single.md index 1a5778e9d7..581b2bcd2e 100644 --- a/docs/usage/single.md +++ b/docs/usage/single.md @@ -57,7 +57,7 @@ render(( ### Custom labels for `enum` fields -This library supports the [`enumNames`](https://github.com/json-schema/json-schema/wiki/enumNames-%28v5-proposal%29) property for `enum` fields, which allows defining custom labels for each option of an `enum`: +This library supports a custom [`enumNames`](https://github.com/rjsf-team/react-jsonschema-form/issues/57) property for `enum` fields, which, however is not JSON-Schema compliant (see below for a compliant approach). The `enumNames` property allows defining custom labels for each option of an `enum`: ```jsx const schema = { @@ -140,4 +140,4 @@ const schema = { render((
), document.getElementById("app")); -``` \ No newline at end of file +```