-
Notifications
You must be signed in to change notification settings - Fork 374
Rrefactor defineWpConfigConsts to work on virtual file system
#415
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
Rrefactor defineWpConfigConsts to work on virtual file system
#415
Conversation
packages/playground/blueprints/src/lib/steps/define-wp-config-consts.ts
Outdated
Show resolved
Hide resolved
|
Thank you @sejas! Something is wrong with the formatting, though. I added a husky pre-commit hook to run |
…to update/refactpr-define-wp-config-consts-step
|
@adamziel, can I merge this branch? |
|
@adamziel, I would appreciate a final review of this PR. Thank you! |
adamziel
left a comment
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.
Almost there, I only left a few nit picks. Thank you for working on this!
packages/playground/blueprints/src/lib/steps/define-wp-config-consts.ts
Outdated
Show resolved
Hide resolved
packages/playground/blueprints/src/lib/steps/define-wp-config-consts.ts
Outdated
Show resolved
Hide resolved
|
Thank you for consolidating that logic @sejas! |
What?
Remove
defineVirtualWpConfigConstsin favor ofdefineWpConfigConsts, adding avirtualizeoption.Why?
Code optimization discussed here #343 (comment)
Testing Instructions
nx preview wp-now start --path=/path/to/wordpress-plugin-or-themeplayground-consts.jsonfile added to the root of wordpress.