scribble-diffusion
scribble-diffusion copied to clipboard
Changed the Scribble component from a function to an arrow function.
Changed the Scribble component from a function to an arrow function.
The original component was defined using the function keyword, but I updated it to use an arrow function instead. This change provides a more concise syntax and also avoids any issues with the binding of the "this" keyword.
I have tested the updated component and verified that it works as expected.
Thanks for considering this change!
@Ben-lad is attempting to deploy a commit to the Replicate Team on Vercel.
A member of the Team first needs to authorize it.
Hi @Ben-lad. It looks like the tests are failing for this and there's a merge conflict. I'm happy to merge this if you're able to sort that stuff out. Thanks!
I'm happy to let you know that I have resolved the issues with the failing tests and the merge conflict.
I have tested the changes thoroughly and everything seems to be working as expected.
Please let me know if there's anything else that needs to be done before merging. Otherwise, I think we're good to go!
Thanks for your help and support throughout this process.
Best regards.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated |
---|---|---|---|---|
scribble-diffusion | ❌ Failed (Inspect) | Mar 3, 2023 at 8:54PM (UTC) |
The build is failing:
$ npm run build
> [email protected] build
> next build
info - Loaded env from /Users/z/git/replicate/scribble-diffusion/.env
Failed to compile.
./pages/scribbles/[id].js
6:15 Error: Parsing error: Only expressions, functions or classes are allowed as the `default` export. (6:15)
The error is due to having two default exports in the same file. On line 6, exporting a functional component with the name "Scribble" using the export default syntax. On line 32, exporting another functional component with the same name, "Scribble", also using the export default syntax
Have fixed the error now you can try again
I'll be happy to hear from you as I fixed the issue
@Ben-lad It looks like you've got a bad merge in there that needs resolving.
Gonna close this due to inactivity. Feel free to open another PR if you want to give this another go.
I'll try that