{"action":"created","issue":{"url":"https://api.github.com/repos/jekyll/jekyll-assets/issues/248","repository_url":"https://api.github.com/repos/jekyll/jekyll-assets","labels_url":"https://api.github.com/repos/jekyll/jekyll-assets/issues/248/labels{/name}","comments_url":"https://api.github.com/repos/jekyll/jekyll-assets/issues/248/comments","events_url":"https://api.github.com/repos/jekyll/jekyll-assets/issues/248/events","html_url":"https://github.com/jekyll/jekyll-assets/issues/248","id":139741519,"number":248,"title":"excluded assets should not be written out","user":{"login":"untra","id":3855429,"avatar_url":"https://avatars.githubusercontent.com/u/3855429?v=3","gravatar_id":"","url":"https://api.github.com/users/untra","html_url":"https://github.com/untra","followers_url":"https://api.github.com/users/untra/followers","following_url":"https://api.github.com/users/untra/following{/other_user}","gists_url":"https://api.github.com/users/untra/gists{/gist_id}","starred_url":"https://api.github.com/users/untra/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/untra/subscriptions","organizations_url":"https://api.github.com/users/untra/orgs","repos_url":"https://api.github.com/users/untra/repos","events_url":"https://api.github.com/users/untra/events{/privacy}","received_events_url":"https://api.github.com/users/untra/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/jekyll/jekyll-assets/labels/pending-feedback","name":"pending-feedback","color":"fbca04"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-03-10T00:11:07Z","updated_at":"2016-03-19T02:56:44Z","closed_at":null,"body":"This may sound like a strange feature to request, but if assets are to be written into the `prefix` folder, and the asset path is listed in the `exclude` directory, then the asset should not be written.\r\n\r\nFor example, if my `_config.yml` looks like:\r\n```yml\r\nexclude:\r\n  - \"assets/styles.css\"\r\nassets:\r\n  prefix: \"/assets\"\r\n```\r\nThen I should expect that `assets/styles.css` is not written.\r\n\r\nIn addtion, if my `_config.yml` looks like:\r\n```yml\r\nexclude:\r\n  - \"assets\"\r\nassets:\r\n  prefix: \"/assets\"\r\n```\r\nThen I should expect that the entirety of the `assets` folder is not written.\r\n\r\n_Why would someone put their assets folder in their `excluded` list?_ My multi-language plugin dynamically modifies the excluded list before kicking off multiple `site.process` jobs. Because jekyll-assets currently builds agnostic to the `excluded` list, It winds up writing files despite my efforts to exclude them.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/jekyll/jekyll-assets/issues/comments/198624231","html_url":"https://github.com/jekyll/jekyll-assets/issues/248#issuecomment-198624231","issue_url":"https://api.github.com/repos/jekyll/jekyll-assets/issues/248","id":198624231,"user":{"login":"untra","id":3855429,"avatar_url":"https://avatars.githubusercontent.com/u/3855429?v=3","gravatar_id":"","url":"https://api.github.com/users/untra","html_url":"https://github.com/untra","followers_url":"https://api.github.com/users/untra/followers","following_url":"https://api.github.com/users/untra/following{/other_user}","gists_url":"https://api.github.com/users/untra/gists{/gist_id}","starred_url":"https://api.github.com/users/untra/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/untra/subscriptions","organizations_url":"https://api.github.com/users/untra/orgs","repos_url":"https://api.github.com/users/untra/repos","events_url":"https://api.github.com/users/untra/events{/privacy}","received_events_url":"https://api.github.com/users/untra/received_events","type":"User","site_admin":false},"created_at":"2016-03-19T02:56:44Z","updated_at":"2016-03-19T02:56:44Z","body":">I'm not trying to be abrasive here, but it seems to me that you broke Jekyll's API and you expect me to backtrack and make it easy for you to push away from how Jekyll behaves by default to support features of which seem to be broken (to me.) A lot of these problems wouldn't exist if generators were used. Then you want me to give you a feature to disable a feature the user wants, that'll never happen because the user wanted the feature and if they didn't want it they wouldn't install it. It's not a default Jekyll Plugin, the user explicitly wanted this feature.\r\n\r\nI'm starting to see that jekyll and jekyll-assets are very decoupled from each other. I was under the impression jekyll-assets would be more confined to jekyll configuration rules. \r\n\r\nIf that's not the case, and there's no desire to implement an off-switch, then I guess this is a feature you don't want to see implemented. :confused: \r\n\r\n\r\n"}}