{"action":"closed","issue":{"url":"https://api.github.com/repos/SilentSpike/ACE3/issues/1","labels_url":"https://api.github.com/repos/SilentSpike/ACE3/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/SilentSpike/ACE3/issues/1/comments","events_url":"https://api.github.com/repos/SilentSpike/ACE3/issues/1/events","html_url":"https://github.com/SilentSpike/ACE3/issues/1","id":76869782,"number":1,"title":"Investigate using functionPriority as a solution for settings/curator module behaviour","user":{"login":"SilentSpike","id":5459452,"avatar_url":"https://avatars.githubusercontent.com/u/5459452?v=3","gravatar_id":"","url":"https://api.github.com/users/SilentSpike","html_url":"https://github.com/SilentSpike","followers_url":"https://api.github.com/users/SilentSpike/followers","following_url":"https://api.github.com/users/SilentSpike/following{/other_user}","gists_url":"https://api.github.com/users/SilentSpike/gists{/gist_id}","starred_url":"https://api.github.com/users/SilentSpike/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SilentSpike/subscriptions","organizations_url":"https://api.github.com/users/SilentSpike/orgs","repos_url":"https://api.github.com/users/SilentSpike/repos","events_url":"https://api.github.com/users/SilentSpike/events{/privacy}","received_events_url":"https://api.github.com/users/SilentSpike/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-05-15T21:55:57Z","updated_at":"2015-06-26T17:56:49Z","closed_at":"2015-06-26T17:56:49Z","body":"As title says. Currently the solution in ACE works, but it might not be the most clean.\r\n\r\nThe settings module should always run before the relevant components of the curator module, this might be possible by simply giving it a lower functionPriority value."}}