-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: markdown formatting #6
Comments
@h0tw4t3r makes sense. Could you link a comment to use as reference? |
TldrAdded cookie-parser to package.json, added AuthGuard to auth.controller, added AuthService to auth.guard.spec.ts. Detailed summary
|
To make sure I understand this, it appears that in most comments it uses backticks to format filenames (ie paradigmxyz/flux#63 (comment)). However in the comment shared above this doesn't seem to be happening. So is it not consistent? |
Yeah, you're absolutely right, it is not consistent. I don't really know, maybe we should lower the temperature and tell it a bit more forcefully to style code? |
@h0tw4t3r Let's see if #7 works, and if that's not enough we can try lowering temp. If the comment shared above is in one of your repos, can you push a commit and see how does the new pr-codex comment look? |
closing this for now, feel free to reopen if needed |
Would be nice to see some
formatted code
as pr-codex sometimes references to the code functions objects etcThe text was updated successfully, but these errors were encountered: