Closed grossbart closed 12 years ago
I think you're right, DefaultService
is probably not needed, but was useful for testing at the time.
I made a change and put it on the change-default-service
branch, it changes the default service to be lazy-loaded from Fdoc.service_path
, which should hopefully help with your ordering problem.
Please check it out and let me know if that fixes things.
I had the same problem, and this fixes it for me. Any chance of merging this?
Yup, I'll do that now, was waiting on confirmation it actually fixed the problem.
Done: 9678ab8a1048146879553651067f47015340566e
Thanks for confirming this, Chris, and for the patch Zach! I'm sorry I didn't confirm this earlier, but I'm on a holiday and wanted to wait until I could confirm it in code, not just theoretically... Cheers, Peter
Am 15.08.2012 um 19:01 schrieb "Zach Margolis" notifications@github.com:
Done: 9678ab8
— Reply to this email directly or view it on GitHub.
In
Fdoc::Service
aDefaultService
is created:This uses the constant
DEFAULT_SERVICE_PATH
which has nothing to do with theFdoc.service_path
setting. This is normally not a problem, but as soon as we try to test with scaffold mode on (FDOC_SCAFFOLD=true
) and theFdoc.service_path
is different from the default, an exception is being thrown:By just removing the
DefaultService
things start to work again, so my question is: is theDefaultService
really needed? It seems to be quite difficult to get a configuration forFdoc.service_path
in there before theDefaultService
is created.