★ wanayoo — archive 1999 https://github.com/allure-framework/allure2/issues/801Nouvelle recherche | Portail wanayoo
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

Feature request: Configuration for date display is MM/DD/YYYY #801

Closed
osmolyar opened this issue Jun 11, 2018 · 4 comments
Closed

Feature request: Configuration for date display is MM/DD/YYYY #801

osmolyar opened this issue Jun 11, 2018 · 4 comments

Comments

@osmolyar
Copy link

@osmolyar osmolyar commented Jun 11, 2018

I'm submitting a ...

  • bug report
  • [ x] feature request
  • support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

-Current behavior: Date in DD/MM/YYYY

What is the expected behavior?

-Would like to have a configuration flag to allow date in MM/DD/YYYY

What is the motivation / use case for changing the behavior?

-Standard US date format

Please tell us about your environment:

Allure version 3.6.0
Test framework webdriverio
Allure adaptor
Generate report using Allure Jenkins plugin

Other information

@aljcalandra
Copy link

@aljcalandra aljcalandra commented Jun 19, 2018

As another user I'd prefer ISO 8601 standard.

@just-boris
Copy link
Member

@just-boris just-boris commented Jun 19, 2018

FYI, the code new Intl.DateTimeFormat().format(new Date()) prints the current date with respect to user's OS settings. Works in all browsers starting from IE11.

This can be a good point to submit a pull-request.

@osmolyar
Copy link
Author

@osmolyar osmolyar commented Jun 19, 2018

@just-boris , are you suggesting making this modification in the allure2 code base and making a pull request? (If so could you please help point to the general area to look in?)

@just-boris just-boris mentioned this issue Jun 19, 2018
1 of 1 task complete
@just-boris
Copy link
Member

@just-boris just-boris commented Jun 19, 2018 •

Oh, well, the change was actually very small (thanks the proper code structure), so I have submitted a change myself: #808

You can pick this up, and test, whether the solution for the feature branch works for you or not.

@baev baev closed this in #808 Jul 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.