-
Notifications
You must be signed in to change notification settings - Fork 23
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
[INTERNAL] generateLibraryManifest: Ignore dependency resources #735
Conversation
They should not be required to generate a manifest.json for a library project.
9e49506
to
877cef5
Compare
@@ -12,23 +11,18 @@ const ReaderCollectionPrioritized = require("@ui5/fs").ReaderCollectionPrioritiz | |||
* @alias module:@ui5/builder.tasks.generateLibraryManifest | |||
* @param {object} parameters Parameters | |||
* @param {module:@ui5/fs.DuplexCollection} parameters.workspace DuplexCollection to read and write files | |||
* @param {module:@ui5/fs.AbstractReader} parameters.dependencies Reader or Collection to read dependency files |
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.
The parameter can also be removed within LibraryBuilder, right?
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.
Done
Good catch! I guess I initially assumed that the dependency resources might be needed to determine the version of library dependencies. But already in the initial PR, those versions have been determined from the project's metadata, not from resources in the dependencies. |
6d57a8b
to
5d7d060
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.
LGTM
They should not be required to generate a manifest.json for a library
project.