Made required context a touch harder

Author: mattpocock

src/07-advanced-patterns/51-required-context.problem.tsx

@@ -14,7 +14,7 @@ const createRequiredContext = () => {
     return contextValue;
   };
 
-  return [useContext, context.Provider] as const;
+  return [useContext, context.Provider];
 };
 
 const [useUser, UserProvider] = createRequiredContext<{

src/07-advanced-patterns/55-as-prop.solution.2.tsx

@@ -5,9 +5,7 @@ export const Component = <TAs extends keyof JSX.IntrinsicElements>(
 ) => {
   const Comp = props.as as string;
 
-  // In this version, we can remove the 'as any' because
-  // TypeScript is able to keep up with the inference
-  return <Comp {...props}></Comp>;
+  return <Comp {...(props as any)}></Comp>;
 };
 
 const example1 = <Component as="a" href="awdawd"></Component>;

src/07-advanced-patterns/56-as-prop-with-custom-components.solution.tsx

@@ -8,13 +8,7 @@ export const Component = <
   } & ComponentProps<T>,
 ) => {
   const Comp = props.as;
-  return (
-    <Comp
-      // The 'as any' is still needed, because 'as' is SO generic
-      // that TypeScript can't handle it.
-      {...props}
-    ></Comp>
-  );
+  return <Comp {...props}></Comp>;
 };
 
 const Link = (props: { href: string; children?: React.ReactNode }) => {