Skip to content
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

Merged
merged 2 commits into from
Apr 21, 2022

Conversation

RandomByte
Copy link
Member

@RandomByte RandomByte commented Apr 20, 2022

They should not be required to generate a manifest.json for a library
project.

@RandomByte RandomByte requested a review from matz3 April 20, 2022 13:27
They should not be required to generate a manifest.json for a library
project.
@RandomByte RandomByte changed the title WIP [INTERNAL] generateLibraryManifest: Ignore dependency resources Apr 20, 2022
@coveralls
Copy link

coveralls commented Apr 20, 2022

Coverage Status

Coverage decreased (-0.001%) to 94.836% when pulling 5d7d060 on dep-less-library-manifest into 4493b13 on next.

@RandomByte RandomByte marked this pull request as ready for review April 20, 2022 13:43
@@ -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
Copy link
Member

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?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@codeworrior
Copy link
Member

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.

matz3
matz3 previously approved these changes Apr 21, 2022
Copy link
Member

@codeworrior codeworrior left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@RandomByte RandomByte merged commit 1e38f2e into next Apr 21, 2022
@RandomByte RandomByte deleted the dep-less-library-manifest branch April 21, 2022 12:00
This was referenced May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants