-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update page.tsx #33
Update page.tsx #33
Conversation
app/page.tsx
Outdated
@@ -6,7 +6,7 @@ import { useState } from "react"; | |||
export default function Dual() { | |||
const { messages, input, handleInputChange, handleSubmit, data } = useChat(); | |||
const { count, setCount } = useState(0); | |||
|
|||
const wawya = "" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one wasn't caught. To be honest, if you could reverse this behavior that would be the most useful. For example, if new empty strings are introduced in a pull, then annotate them with a warning. If it is merged in, then in future pulls it should be ignored. That would be excellent.
I'm pretty sure there is a way to annotate only in the files view instead of showing on the conversation view as well like we see here. Can you look into that? Its some type of built in GitHub actions methods I believe. As you can see the conversation view is getting cluttered again. |
I was going to mention that but yeah I'll look into it |
No description provided.