-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Factor out the config file compile step #4867
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/keystonejs/keystone-next-docs/52g5yc88z |
🦋 Changeset detectedLatest commit: 0d666f6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 12 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
0e2e08d
to
25c0ac8
Compare
25c0ac8
to
303af16
Compare
export const formatSource = (src: string, parser: 'babel' | 'babel-ts' = 'babel') => | ||
prettier.format(src, { parser, trailingComma: 'es5', singleQuote: true }); | ||
|
||
const generateKeystoneConfig = async (projectAdminPath: string) => { |
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.
const generateKeystoneConfig = async (projectAdminPath: string) => { | |
const generateKeystoneConfigReexport = async (projectAdminPath: string) => { |
v much a nit, I just want it to be clear to readers that it's not generating a keystone config, it's re-exporting the user's config
This will allow us to conditionally generate/build the Admin UI, without losing our compiled config file.