{"action":"created","issue":{"url":"https://api.github.com/repos/tailwindcss/tailwindcss/issues/523","repository_url":"https://api.github.com/repos/tailwindcss/tailwindcss","labels_url":"https://api.github.com/repos/tailwindcss/tailwindcss/issues/523/labels{/name}","comments_url":"https://api.github.com/repos/tailwindcss/tailwindcss/issues/523/comments","events_url":"https://api.github.com/repos/tailwindcss/tailwindcss/issues/523/events","html_url":"https://github.com/tailwindcss/tailwindcss/issues/523","id":342578949,"node_id":"MDU6SXNzdWUzNDI1Nzg5NDk=","number":523,"title":"[Feature proposal] configurable class names","user":{"login":"davidDuymelinck","id":3919133,"node_id":"MDQ6VXNlcjM5MTkxMzM=","avatar_url":"https://avatars2.githubusercontent.com/u/3919133?v=4","gravatar_id":"","url":"https://api.github.com/users/davidDuymelinck","html_url":"https://github.com/davidDuymelinck","followers_url":"https://api.github.com/users/davidDuymelinck/followers","following_url":"https://api.github.com/users/davidDuymelinck/following{/other_user}","gists_url":"https://api.github.com/users/davidDuymelinck/gists{/gist_id}","starred_url":"https://api.github.com/users/davidDuymelinck/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davidDuymelinck/subscriptions","organizations_url":"https://api.github.com/users/davidDuymelinck/orgs","repos_url":"https://api.github.com/users/davidDuymelinck/repos","events_url":"https://api.github.com/users/davidDuymelinck/events{/privacy}","received_events_url":"https://api.github.com/users/davidDuymelinck/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2018-07-19T04:56:22Z","updated_at":"2018-11-10T12:11:34Z","closed_at":null,"author_association":"NONE","body":"I read the #102 issue for custom class names. But I found the solution a bit lacking. \r\n\r\n> disabling an existing module and adding your own plugin\r\n\r\nIf you want to change one class from a plugin, you need to copy paste the plugin and add the change. And what if you want to change 20 plugins?\r\n\r\nSo I forked the project and came up with a way to make all classes configurable. https://github.com/davidDuymelinck/tailwindcss\r\n\r\nBasically I added a new key to the config object, modifyClassNames. The value of the key is an object which has the module names as keys. \r\n\r\nEach module has a prefix and modifier key. The prefix has a string value. The modifier key is an object with a key from the plugin and as value the class name after the prefix.\r\n\r\n```\r\nmodifyClassNames: {\r\n   whitespace: {\r\n        prefix: 'ws-',\r\n        modifier: {\r\n             normalWord: 'wrap-word-normal'\r\n        }\r\n   }\r\n}\r\n```\r\nThis example is for the class name that is now generated as break-normal.\r\n\r\nFor the modifier keys I wanted to stay as close to the style value as possible to make the configuration as easy as possible. An other example of this is the `noDecoration` key for the current class name no-underline.\r\n\r\nI understand this is a nice to have for the maintainers. I just wanted to show the solution I came up with, to find out if there are other people who still want class name configuration included in Tailwind CSS? "},"comment":{"url":"https://api.github.com/repos/tailwindcss/tailwindcss/issues/comments/437579638","html_url":"https://github.com/tailwindcss/tailwindcss/issues/523#issuecomment-437579638","issue_url":"https://api.github.com/repos/tailwindcss/tailwindcss/issues/523","id":437579638,"node_id":"MDEyOklzc3VlQ29tbWVudDQzNzU3OTYzOA==","user":{"login":"xwero","id":496309,"node_id":"MDQ6VXNlcjQ5NjMwOQ==","avatar_url":"https://avatars1.githubusercontent.com/u/496309?v=4","gravatar_id":"","url":"https://api.github.com/users/xwero","html_url":"https://github.com/xwero","followers_url":"https://api.github.com/users/xwero/followers","following_url":"https://api.github.com/users/xwero/following{/other_user}","gists_url":"https://api.github.com/users/xwero/gists{/gist_id}","starred_url":"https://api.github.com/users/xwero/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xwero/subscriptions","organizations_url":"https://api.github.com/users/xwero/orgs","repos_url":"https://api.github.com/users/xwero/repos","events_url":"https://api.github.com/users/xwero/events{/privacy}","received_events_url":"https://api.github.com/users/xwero/received_events","type":"User","site_admin":false},"created_at":"2018-11-10T12:11:34Z","updated_at":"2018-11-10T12:11:34Z","author_association":"NONE","body":"@JordanMartinez my solution provides of the one-is-replaced-by-another type. The reason is that marketeers don't care about which technology you use, as long as they can be more productive everything is fine.\r\nThe only thing that slows down your productivity is that you can't refer to the Tailwind documentation. You have to write your own.\r\n\r\nI mentioned that Tailwind provides a way to change classes. But if you have to change a lot of classes, it's too much boilerplate.\r\nI understand the maintainers that a more DX solution is low on the priority list. \r\n\r\nI'm going to make an effort to keep my fork up to date, so that other people can use it."}}
{"actor":{"display_login":"xwero"}}