-
Notifications
You must be signed in to change notification settings - Fork 364
Run linter in deploy tool #417
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
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Doing things in parallel looks good! I'll polish this up later |
acf0448
to
b3319df
Compare
b3319df
to
45b4abf
Compare
@@ -0,0 +1 @@ | |||
ignore-workspace-root-check=true |
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.
allows installing libraries in the main chef project without warning (needed because now that this is a little pnpm monorepo)
} from './messages'; | ||
import { createScopedLogger } from '~/utils/logger'; | ||
|
||
const logger = createScopedLogger('history'); |
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.
just cleanup so these aren't always printed
I'm not confident about linting not making things worse so I'll make another PR that's everything here except that. |
All the extra stuff I added in #417 without the linting
f9a362e
to
be50c7f
Compare
Run eslint in the deploy tool. This doesn't help much yet, but it adds a path for adding eslint rules specific to the failure modes we're seeing.
We'd try to catch things that have no type errors with these lint rules currently, since lint errors are only reported to the LLM if both typechecks fail. Alternately we could report eslint failures in addition to type errors.