-
Notifications
You must be signed in to change notification settings - Fork 331
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
Build tasks: Clearly show subdirectory paths #3370
Conversation
0f69491
to
bbb70de
Compare
bbb70de
to
94ae8ec
Compare
94ae8ec
to
01f19fb
Compare
01f19fb
to
1039b99
Compare
1039b99
to
d4db145
Compare
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.
I think that makes things a little more obvious 🙌🏻 Wondering if we'd need helpers to remove the many join(path.xyz,...)
that we do into a path.xyz(...)
but that can be done in a further PR 😄
@@ -20,7 +20,7 @@ export default async () => { | |||
.filter(filterPath([`${componentName}/macro.njk`])) | |||
|
|||
return { | |||
importFrom: slash(relative(configPaths.src, join(configPaths.components, macroPath))), | |||
importFrom: slash(relative(paths.src, join(paths.src, 'govuk/components', macroPath))), |
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.
question It's not your change, but isn't that equivalent to join('govuk/components', macroPath)
?
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.
@romaricpascal Spot on! Hidden away by configPaths.components
until now
Will fix before merging, thanks again
This commit removes non-root paths from the paths config It’s now easy to determine “source” versus “review app” directories ```js join(paths.src, 'govuk/assets') join(paths.src, 'govuk/components') join(paths.app, 'views') join(paths.app, 'views/layouts') ```
d4db145
to
f14899f
Compare
This PR helps to clearly show our build paths as part of:
Whilst pairing on #3318 it wasn't obvious which areas of the repo are being copied, written or built from config paths
For example, what's the difference between these three?
configPaths.components
join(configPaths.package, 'govuk/components')
join(configPaths.package, 'govuk-esm/components')
I've ensured that only top-level paths are found in config/paths.js so their locations are clear:
Top level
Source
Review app