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

Use i18n for datepicker format #3321

Merged
merged 1 commit into from
Feb 16, 2023
Merged

Conversation

coorasse
Copy link
Contributor

@coorasse coorasse commented Aug 30, 2019

This PR fixes #2721.
I'd like to fix it already in version 2.7 and release a 2.7.4 if possible.
The datepicker should take the js_format from i18n file (not in use anywhere else).
I'll open also a PR on solidus_i18n to set it already correctly for the other locales.

I am not sure if this is a breaking change. If someone has overridden js_format with something weird it will probably stop working.

@kennyadsl
Copy link
Member

Thanks, @coorasse. I'm rerunning specs, failures do not seem related but I did never see those before. Let's see what happens.

@aldesantis
Copy link
Member

@coorasse we're going through old PRs and this seems like a fix we want to have. Unfortunately, 2.7 is not maintained anymore, so I don't know if it makes sense to add it there. If you still have the time, would you be willing to rebase against master or 2.8?

@kennyadsl kennyadsl added the type:bug Error, flaw or fault label Aug 24, 2022
@kennyadsl
Copy link
Member

For reference, if this is still valid, we should make this PR against master (and eventually backport).

@kennyadsl kennyadsl added changelog:solidus_backend Changes to the solidus_backend gem Needs Work labels Aug 24, 2022
@waiting-for-dev waiting-for-dev added the changelog:solidus_core Changes to the solidus_core gem label Aug 30, 2022
@kennyadsl kennyadsl changed the base branch from v2.7 to master February 16, 2023 11:07
@kennyadsl kennyadsl requested a review from a team as a code owner February 16, 2023 11:07
@kennyadsl
Copy link
Member

@coorasse I rebased this against master and resolved a conflict. If specs pass, I'll go head and add the backport labels to have this on recent support versions of Solidus and will ask for a review by other core team members. Thanks again!

@codecov
Copy link

codecov bot commented Feb 16, 2023

Codecov Report

Merging #3321 (042ea36) into master (9757964) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3321   +/-   ##
=======================================
  Coverage   86.69%   86.69%           
=======================================
  Files         578      578           
  Lines       14673    14673           
=======================================
  Hits        12721    12721           
  Misses       1952     1952           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@kennyadsl
Copy link
Member

@waiting-for-dev do you have any idea about why ensure and triage actions have not been triggered here? 🤔

@waiting-for-dev
Copy link
Contributor

@waiting-for-dev do you have any idea about why ensure and triage actions have not been triggered here? 🤔

@kennyadsl, I think the synchronize activity type doesn't include changing the base branch. However, making a change to the commits on the head branch does. I forced another push and the workflow has run now.

@kennyadsl kennyadsl merged commit 7be1937 into solidusio:master Feb 16, 2023
@kennyadsl kennyadsl changed the title Fix issue with available_on datepicker Use i18n for datepicker format Feb 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog:solidus_backend Changes to the solidus_backend gem changelog:solidus_core Changes to the solidus_core gem type:bug Error, flaw or fault
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Not update available on date
5 participants