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

[BREAKING] LibraryFormatter: Ignore manifest.json of nested apps #392

Merged
merged 1 commit into from
Mar 24, 2020

Conversation

RandomByte
Copy link
Member

@RandomByte RandomByte commented Dec 30, 2019

If a library contains a nested application project or similar, do not
assume that projects manifest.json to be relevant for the library itself
in case it does not feature a manifest.json.
Instead try to identify such situations by checking whether the
.library file and the manifest.json are on the same directory level.

BREAKING CHANGE:
If a library contains both, a manifest.json and .library file, they must
either be located in the same directory or the manifest.json is ignored.
In cases where the manifest.json is located on a higher level or
different directory on the same level than a .library file, an exception
is thrown.

@coveralls
Copy link

coveralls commented Mar 14, 2020

Coverage Status

Coverage increased (+0.06%) to 91.201% when pulling 7a435c2 on library-handle-nested-apps-manifest into 0bf7880 on master.

@RandomByte RandomByte force-pushed the library-handle-nested-apps-manifest branch from e7239a8 to 6ac1e3d Compare March 14, 2020 12:32
@RandomByte RandomByte force-pushed the library-handle-nested-apps-manifest branch from 6ac1e3d to c79169e Compare March 24, 2020 00:11
@RandomByte RandomByte changed the title [WIP] LibraryFormatter: Ignore manifest.json of nested apps [BREAKING] LibraryFormatter: Ignore manifest.json of nested apps Mar 24, 2020
@RandomByte RandomByte marked this pull request as ready for review March 24, 2020 00:11
@RandomByte
Copy link
Member Author

I think it would make sense to add this to the 2.0 release.

@RandomByte RandomByte force-pushed the library-handle-nested-apps-manifest branch from c79169e to 93a8171 Compare March 24, 2020 09:58
If a library contains a nested application project or similar, do not
assume that projects manifest.json to be relevant for the library itself
in case it does not feature a manifest.json.
Instead try to identify such situations by checking whether the
.library file and the manifest.json are on the same directory level.

BREAKING CHANGE:
If a library contains both, a manifest.json and .library file, they must
either be located in the same directory or the manifest.json is ignored.
In cases where the manifest.json is located on a higher level or
different directory on the same level than a .library file, an exception
is thrown.
@RandomByte RandomByte force-pushed the library-handle-nested-apps-manifest branch from 93a8171 to 7a435c2 Compare March 24, 2020 10:20
@RandomByte RandomByte merged commit 846e929 into master Mar 24, 2020
@RandomByte RandomByte deleted the library-handle-nested-apps-manifest branch March 24, 2020 13:46
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.

3 participants