Hello!
The reason for the question is so that urql doesn't necessarily opt-out us of automatic static optimization.
According to the docs:
This determination is made by the absence of
getServerSidePropsandgetInitialPropsin the page.
So if it were possible to select getStaticProps we would have the best of both world. 馃槉 But I'm just guessing for now!
Not yet! But I see that this is an important feature we should add 馃憤
Looking forward to this! If it was in place, I would have jumped to try this out right away!
This RFC in next.js is related to this request and if that gets in it would make new options for this change.
This was implemented in https://github.com/FormidableLabs/urql/pull/797 and will be part of the next-urql v1 release
Most helpful comment
This was implemented in https://github.com/FormidableLabs/urql/pull/797 and will be part of the
next-urql v1release