{"action":"created","issue":{"url":"https://api.github.com/repos/feathersjs/feathers-rest/issues/23","repository_url":"https://api.github.com/repos/feathersjs/feathers-rest","labels_url":"https://api.github.com/repos/feathersjs/feathers-rest/issues/23/labels{/name}","comments_url":"https://api.github.com/repos/feathersjs/feathers-rest/issues/23/comments","events_url":"https://api.github.com/repos/feathersjs/feathers-rest/issues/23/events","html_url":"https://github.com/feathersjs/feathers-rest/issues/23","id":142081618,"number":23,"title":"Add the ability for services to be internal only.","user":{"login":"pierretasci","id":11216346,"avatar_url":"https://avatars.githubusercontent.com/u/11216346?v=3","gravatar_id":"","url":"https://api.github.com/users/pierretasci","html_url":"https://github.com/pierretasci","followers_url":"https://api.github.com/users/pierretasci/followers","following_url":"https://api.github.com/users/pierretasci/following{/other_user}","gists_url":"https://api.github.com/users/pierretasci/gists{/gist_id}","starred_url":"https://api.github.com/users/pierretasci/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pierretasci/subscriptions","organizations_url":"https://api.github.com/users/pierretasci/orgs","repos_url":"https://api.github.com/users/pierretasci/repos","events_url":"https://api.github.com/users/pierretasci/events{/privacy}","received_events_url":"https://api.github.com/users/pierretasci/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-03-19T16:56:42Z","updated_at":"2016-03-19T21:28:40Z","closed_at":"2016-03-19T19:08:46Z","body":"The service and hooks abstraction in feathers is awesome and really powerful. So much in fact, that I want to use it more extensively. I want to be able to create internal only services that have useful server side logic like a file storage service or a field validator service. \r\n\r\nThe problem becomes that I have to expose that service's CRUD methods as rest methods. I don't necessarily want to do that. So far I have taken to namespacing my internal services with an _service_name_. This is obviously not an ideal solution. \r\n\r\nHaving peeked into the logic that hooks a service up to express, it seems like it wouldn't be hard to just skip that part if some flag is set on the service, or if the name is _service_name_ or some other construct.\r\n\r\nThanks!"},"comment":{"url":"https://api.github.com/repos/feathersjs/feathers-rest/issues/comments/198787416","html_url":"https://github.com/feathersjs/feathers-rest/issues/23#issuecomment-198787416","issue_url":"https://api.github.com/repos/feathersjs/feathers-rest/issues/23","id":198787416,"user":{"login":"daffl","id":338316,"avatar_url":"https://avatars.githubusercontent.com/u/338316?v=3","gravatar_id":"","url":"https://api.github.com/users/daffl","html_url":"https://github.com/daffl","followers_url":"https://api.github.com/users/daffl/followers","following_url":"https://api.github.com/users/daffl/following{/other_user}","gists_url":"https://api.github.com/users/daffl/gists{/gist_id}","starred_url":"https://api.github.com/users/daffl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/daffl/subscriptions","organizations_url":"https://api.github.com/users/daffl/orgs","repos_url":"https://api.github.com/users/daffl/repos","events_url":"https://api.github.com/users/daffl/events{/privacy}","received_events_url":"https://api.github.com/users/daffl/received_events","type":"User","site_admin":false},"created_at":"2016-03-19T21:28:40Z","updated_at":"2016-03-19T21:28:40Z","body":"It's a great question and granted, it is a little hidden. I created a follow-up issue in https://github.com/feathersjs/feathers-docs/issues/93 and will add it to the FAQ."}}