You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current the library requires you to specify a log file within the config file - this is not ideal as you may well not know the folder ahead of runtime to put into the file. (e.g. you're in a Symfony app and the folder could be anywhere in relation to the config file).
What I did was set the parameter to './' in the file and then planned to override it with the next line of code, not ideal, but workable.
However, that doesn't work as it assumes the file is already existing when you call setLogPath(). Can you change it so that it doesn't assume the file exists, or at the very least, if it doesn't exist either ignore the error (and don't raise an exception) or simply create it.
Cheers.
The text was updated successfully, but these errors were encountered:
I see what you mean. I think a good idea would be to add log link as a supported key in the passed config array (discussed in #97). In the meantime, pull request #102 was just created, which creates the log file if it does not exist.
Cheers. I'm actually looking at seeing if I can do the config array change now - it depends on how much the config is used internally. if I get it working, I'll create a pull request (I think that's the term, I'm more used to SVN than git).
Current the library requires you to specify a log file within the config file - this is not ideal as you may well not know the folder ahead of runtime to put into the file. (e.g. you're in a Symfony app and the folder could be anywhere in relation to the config file).
What I did was set the parameter to './' in the file and then planned to override it with the next line of code, not ideal, but workable.
However, that doesn't work as it assumes the file is already existing when you call setLogPath(). Can you change it so that it doesn't assume the file exists, or at the very least, if it doesn't exist either ignore the error (and don't raise an exception) or simply create it.
Cheers.
The text was updated successfully, but these errors were encountered: