Skip to content
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 filename treatment - Related to issue #55 #58

Closed
wants to merge 3 commits into from

Conversation

velenoise
Copy link

Added support to extension on file name
Added options to customize separator apart from date format
Added option for default extension, in case it's ommited from the file
name

Added support to extension on file name
Added options to customize separator apart from date format
Added option for default extension, in case it's ommited from the file
name
@velenoise
Copy link
Author

I'm not familiar with travis to understand what may have failed, if you want to give me some guidelines I'll be happy to correct my pull request. I'm sure it's working correctly because I implemented it for a live project.

@mattberther
Copy link
Member

@velenoise thanks for the PR. Can you make sure that the unit tests are passing -- you can do so by running npm test from the root of the project. Ill look for an updated commit that makes the tests pass before I merge the PR.

Thanks!

Copy link

@frode frode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

extension after datepattern is very welcome 👍

@velenoise
Copy link
Author

I've been quite busy with some other stuff, but I'll try to get back to it this week.

@kiermasp
Copy link

Hi guys, Please can sb merge this ? We have live project where we use this plugin and I really need this feature. Thanks.

@kiermasp
Copy link

kiermasp commented Mar 3, 2017

Any chance to get this merged?

@velenoise
Copy link
Author

@kiermasp Feel free to download from my branch while it's not merged: https://github.com/velenoise/winston-daily-rotate-file/tree/filename-adjustments. It seems some new test checks were included that are failing on my branch now, I'll have to take some time later to review them, but probably it's just that the tests are waiting for the old format as a result.

@mattberther
Copy link
Member

@velenoise I'd like to get this merged. However, I also need to make sure that we're not changing existing unit tests to make this work. The existing unit tests describe functionality that users of the library may have come to expect.

This may mean that we need to add an option that users can select to leverage your code path.

So, as I see it, there are a couple things left:

  • Revert the code changes to the unit test file(s)
  • Create new unit tests that describe the expected functionality from the PR
  • Update the implementation to make sure ALL unit tests pass
  • Run npm test locally to ensure everything is passing
  • Push the changes to this PR

Thanks!

@sandman45
Copy link

sandman45 commented May 18, 2017

@velenoise awesome!!! this is what i need :D

I am using your branch.. once its merged I assume you will delete it? I got it on star and watching it so it should notify me.

thanks

@mattberther
Copy link
Member

Some long-overdue refactoring of the transport has occurred. Closing this PR in favor of #107.

@mattberther mattberther closed this Nov 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants