-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improved logging #149
Improved logging #149
Conversation
- Based on "winston" logging library - Removed no longer needed lodash - Locked npm dependencies to most recent major versions to avoid installs breaking due to node module updates
- Break out reading of settings in js and remove it from shell scripts - Pick up config from Logger via Configuration class
Nice work! I have been missing prepended timestamps! 😀 👍 |
Great work! One small thing though, I'd like the file names to conform to the rest of the project in using lower case names. Nothing major :-) |
I can change it for sure, however the semantics is different. The two new files export the class directly and is used I personally prefer the "follow default export naming convention" mentioned for example here AirBnB style guide and also strive for "one export per file", but I realize it's a bit different than today. Either way I think it's good to set a pattern. What do you think, how should we proceed? Always export a "wrapper" ( On a side note I am personally like named exports than default exports, so I would normally do similar to how you have done so far (with other syntax) |
I agree with you 100% regarding exports and classes, I like the AirBnB style. Think this addon has grown a bit from my initial tests :-) therefore the structure today is quite poor. When working with React and such, you normally (at least if you scan the internet a few seconds :-D) use default exports if you don't have more than one export. I can't say that I'm pro this or that, as long as we follow the same standard through out the whole project. |
So - what's the decision :) I'm quite fine with either way forward, but I think it's good to decide "something". |
Lets follow the AirBnB style guide and rework any files not conforming to that. That would also mean that we use default exports and strive for a single export per file. |
Adjusted code style on top of this PR, but broke out in separate branch/pr for comparison purposes. Is a bit opinionated and touches a lot of files, feel free to reject or suggest major changes! |
Completely rewritten logging for js to improve code structure and user experience
winston
Also breaks out configuration fetching in js, removes the redundant
plejd.json
file and cleans up code fromplejd.sh
.