Next

What is the improvement or update you wish to see?

I would like to clarify the API documentation for the return value of getServerSideProps.

Is there any context that might help us understand?

I was implementing user authentication on my website, and I was trying to restrict access to the login and signup pages if the user is logged in. To do so, I am implementing this `getServerSideP

What do you want and why?

If a user has a react-final-form with a JS Set (or Map) in the initial values, the form resets on some activities, e.g. switching to another tab.

Possible implementation(s)

This can be fixed by using the initialValuesEqual prop:

import deepEqual from "fast-deep-equal"

    <FinalForm
      initialValues={initialValues}
      initialValues

Question 💬

It seems that the error messages are not typed. If we could have typed errors, it could further improve customizations.

According to what I found here: https://github.com/nextauthjs/next-auth/blob/82447f8e3ebc7004cf91121725b4f5970d2276d8/src/core/pages/signin.tsx#L42

An example I can think of is:

export type ErrorType = 
  'SignIn' | 
  'OAuthSignin'
``

Summary

InlineImage component should have cursor: pointer style when CMS is enabled.
(Currently is only ever has the normal default cursor.)
The pointer cursor indicates to the user that clicking it will trigger some action.
In this case that action is opening a Media Manager dialog.

Motivation

I did my first introduction/training of a TinaCMS application to a person, and

Without all the marketing.

Right now the wishlist page shows "Your wishlist is empty" before showing your wishlist items, that should be a loading state instead.

Would be supercool to have "BlogPosting" as article JSON-LD type.

From the Google Docs (https://developers.google.com/search/docs/data-types/article#non-amp):

Article objects must be based on one of the following schema.org types: Article, NewsArticle, BlogPosting. (https://schema.org/BlogPosting)

I tried to use "BlogJsonLd" as type for Blogposts, but the Google Rich Result Test (https:

Characters like č ć ž š đ use a fallback font instead of the original one. I believe this issue was not present in the v1. Fonts such as Lato or Montserrat definitely support accented characters, so I think this is a bug.

Issue Summary

Building with serverless results in an error:

Build error occurred
TypeError: Class extends value undefined is not a

Things like Optional Chaining should be transpiled for e.g. node 12 compatibility: https://esbuild.github.io/content-types/#javascript. We should choose es2016 for all packages.