Skip to content
This repository has been archived by the owner on May 24, 2023. It is now read-only.

quick readme update for file exclusion #22

Closed
wants to merge 4 commits into from
Closed

quick readme update for file exclusion #22

wants to merge 4 commits into from

Conversation

agraebe
Copy link

@agraebe agraebe commented Jan 13, 2016

No description provided.

@CLAassistant
Copy link

CLA assistant check
All committers have accepted the CLA.

@@ -221,6 +222,8 @@ Default: component namespace path + `/**` (e.g. `my/app/**`)
Glob pattern(s) for files that should be included into the preload.
Patterns are based on all available resources (see [resources](#resources)).

**Note:** You can exclude files by prepending the exclamation mark, like so: ```!my/app/ignore.js```.

### libraries

See [components](#components). Auto mode is looking for `library.js` files.
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we should also add a note here. As the current default pattern does only include **/*.fragment.json files but not library-preload.json we don't really need a equivalent exclude for libraries.

@matz3
Copy link
Contributor

matz3 commented Jan 18, 2016

When doing the review I again thought about this change and there might be a use case to include Component-preload.js files.

  • Packaging sub-components into a root component
  • Packaging libraries into components or vice versa

I would rather do a check independent of the include/exclude patterns to prevent including an output file (Component-preload.js / library-preload.json) which is in the same folder as the targeted Component or Library (Component.js / library.js).

@matz3
Copy link
Contributor

matz3 commented Jan 28, 2016

@agraebe do you want to follow up on this?
Otherwise I would do a change based on my last comments.

@agraebe
Copy link
Author

agraebe commented Jan 28, 2016

I think we should approach with your suggestions, sorry for the late response!

@matz3
Copy link
Contributor

matz3 commented Feb 2, 2016

See #25 (documentation update is missing there. I'll add that later). Let me know if this suits your needs.

@matz3
Copy link
Contributor

matz3 commented Apr 25, 2016

As there was no further feedback I merged #25 which will be included in the next release. I did not adopt the README.md as the behavior should be quite obvious.

@matz3 matz3 closed this Apr 25, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants