How do you resolve issues with the Authentication and Access Control documentation in KeystoneJS? 

To consume a REST API through KeystoneJS, you can create custom resolvers or hooks within your schema. This is a simple method that makes use of custom GraphQL resolvers:

• Define a custom GraphQL resolver in your KeystoneJS schema.
• Use an HTTP client like axios or node-fetch within the resolver to make API calls to the REST endpoint.
• Return the fetched data as part of your query or mutation response.

Example:

This query will fetch data from the external API and expose it through your Keystone GraphQL schema.

You can set a default value for the calendarDay field in KeystoneJS by providing the defaultValue option when defining the field in your schema. For example:

This will ensure that the field is pre-filled with a specific default date, such as the current date. You can also set other default values by modifying the function accordingly.

To make the document field show up bigger by default in KeystoneJS, you can change the admin dashboard's appearance. KeystoneJS doesn’t have a built-in way to do this directly, but you can use the ui option in your setup to change how fields show and work. This could let you make them open or bigger automatically with some custom code. You might need to add some extra features and create your own components to do this.

Using hooks like <code>resolveInput</code>, you can retrieve and send dynamic data to custom fields in KeystoneJS, allowing you to edit the data before storing it to the database.

In KeystoneJS, you can throw a custom error by returning an error object inside the schema's access control logic, like in <code>isAccessible</code>