{"action":"created","issue":{"url":"https://api.github.com/repos/bcit-ci/CodeIgniter4/issues/186","repository_url":"https://api.github.com/repos/bcit-ci/CodeIgniter4","labels_url":"https://api.github.com/repos/bcit-ci/CodeIgniter4/issues/186/labels{/name}","comments_url":"https://api.github.com/repos/bcit-ci/CodeIgniter4/issues/186/comments","events_url":"https://api.github.com/repos/bcit-ci/CodeIgniter4/issues/186/events","html_url":"https://github.com/bcit-ci/CodeIgniter4/issues/186","id":166702041,"number":186,"title":"Config Settings Usability","user":{"login":"jim-parry","id":3203951,"avatar_url":"https://avatars.githubusercontent.com/u/3203951?v=3","gravatar_id":"","url":"https://api.github.com/users/jim-parry","html_url":"https://github.com/jim-parry","followers_url":"https://api.github.com/users/jim-parry/followers","following_url":"https://api.github.com/users/jim-parry/following{/other_user}","gists_url":"https://api.github.com/users/jim-parry/gists{/gist_id}","starred_url":"https://api.github.com/users/jim-parry/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jim-parry/subscriptions","organizations_url":"https://api.github.com/users/jim-parry/orgs","repos_url":"https://api.github.com/users/jim-parry/repos","events_url":"https://api.github.com/users/jim-parry/events{/privacy}","received_events_url":"https://api.github.com/users/jim-parry/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-07-20T22:59:58Z","updated_at":"2016-07-21T04:59:47Z","closed_at":"2016-07-21T04:59:47Z","body":"Is there a reason why all of the application/Config classes should not be in system/Config?\r\nIt seems to me that the ones in application/Config should extend the ones under system/, and contain commented properties/settings, and methods, that a developer could over-ride. Detailed descriptions could be in either place.\r\n\r\nThe way it sits now, any changes to any configs in the framework will require a developer to reintegrate the \"new, improved\" stuff manually into the application/Config folder in each of their projects, rather than just having to worry about whatever changed.\r\n\r\nIf the intent is that a \".env\" file provide for project-level customization, why do we need the classes in application/config.\r\n\r\nThe details might differ slightly between config classes, but the above feels like a reasonable & O-O approach to me."},"comment":{"url":"https://api.github.com/repos/bcit-ci/CodeIgniter4/issues/comments/234157185","html_url":"https://github.com/bcit-ci/CodeIgniter4/issues/186#issuecomment-234157185","issue_url":"https://api.github.com/repos/bcit-ci/CodeIgniter4/issues/186","id":234157185,"user":{"login":"jim-parry","id":3203951,"avatar_url":"https://avatars.githubusercontent.com/u/3203951?v=3","gravatar_id":"","url":"https://api.github.com/users/jim-parry","html_url":"https://github.com/jim-parry","followers_url":"https://api.github.com/users/jim-parry/followers","following_url":"https://api.github.com/users/jim-parry/following{/other_user}","gists_url":"https://api.github.com/users/jim-parry/gists{/gist_id}","starred_url":"https://api.github.com/users/jim-parry/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jim-parry/subscriptions","organizations_url":"https://api.github.com/users/jim-parry/orgs","repos_url":"https://api.github.com/users/jim-parry/repos","events_url":"https://api.github.com/users/jim-parry/events{/privacy}","received_events_url":"https://api.github.com/users/jim-parry/received_events","type":"User","site_admin":false},"created_at":"2016-07-21T04:59:47Z","updated_at":"2016-07-21T04:59:47Z","body":"Ok. I will table the suggestion for now, and re-examine the notion once we have progressed much further along  :-)"}}
{"actor":{"display_login":"jim-parry"}}