Skip to content

Conversation

RandomByte
Copy link
Member

This can lead to issues where a custom task creates resources using a
different version of @ui5/fs. These reosurces will fail the instanceof
check that was implemented here.

Instead of checking for the class, we now validate that the resource has
a path. The path is currently the only relevant attribute for
ResourceTagCollection and mandatory for Resources.

Resolves https://github.com/SAP/ui5-fs/issues/269

This can lead to issues where a custom task creates resources using a
different version of @ui5/fs. These reosurces will fail the instanceof
check that was implemented here.

Instead of checking for the class, we now validate that the resource has
a path. The path is currently the only relevant attribute for
ResourceTagCollection and mandatory for Resources.

Resolves https://github.com/SAP/ui5-fs/issues/269
@coveralls
Copy link

Coverage Status

Coverage increased (+0.2%) to 87.739% when pulling 2dd8b00 on no-resource-instance-check into a2021ac on master.

@RandomByte RandomByte merged commit c52c9f7 into master Aug 12, 2020
@RandomByte RandomByte deleted the no-resource-instance-check branch August 12, 2020 10:56
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.

Invalid Resource: Must be instance of @ui5/fs.Resource

3 participants