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

Calendar - add option to change step size in yearpicker #15419

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bjuergens
Copy link

@bjuergens bjuergens commented May 1, 2024

Hi,

This is my first time contribution. I am not sure about the standard operating procedure. If I made a mistake, please point me in the right direction.

As suggested by the contribution-guidelines, I opened a discussion: https://github.com/orgs/primefaces/discussions/1780

After reading the text in the PR-template (see below), I am no longer certain such a discussion is necessary, since this is a small scale feature.

Feature Requests

Due to company policy, we are unable to accept feature request PRs with significant changes as such cases has to be implemented by our team following our own processes.
Smaller scaled feature implementations such as adding a property to a component will be considered for merging.

I think this qualifies as "Smaller scaled feature implementations".


Here is what this PR does:

It changes the default step-size for the year picker from 10 to 20 [1]. And it adds a input-parameter to change the stepsize [2]

In the discussion I explain, why I think this feature is usefull. (But I guess it would be ok to let the discussion-page die, and instead move discussions here)

[1]:

grafik

[2]:

2024-05-01_17-42 yearpickerstep

Copy link

vercel bot commented May 1, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
primeng ⬜️ Ignored (Inspect) Visit Preview May 1, 2024 9:03pm

@RogueTea
Copy link
Contributor

RogueTea commented May 1, 2024

Could you please confirm how this appears on mobile and tablet screens? I'm concerned that the default step size might cause some parts to be cut off.

}

incrementDecade() {
this.currentYear = this.currentYear + 10;
incrementYearpickerstep() {
Copy link
Contributor

Choose a reason for hiding this comment

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

same here, incrementYearPickerStep

Copy link
Author

Choose a reason for hiding this comment

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

I changed it to "incrementYearPickerStep". ("decrement-" and "stepYearpicker" analoge)

I am not sure about the wording. Maybe "incrementYearPicker" (without "-step") would be better? Or maybe "incrementYearPickerRange" or "incrementYearPickerValues"?

@bjuergens
Copy link
Author

size 20 on firefox/galaxy s10:
grafik

size 20 on chrome/galaxy s8
grafik

size 10 on firefox/galaxy s10:
grafik

I feel like these buttons are too small to be comfortable on mobile. But I guess that would be a different issue.

@bjuergens
Copy link
Author

sorry for forcepushing.

I squashed some commits, that would add clutter individually. Also I forgot to setup name/mail for git on this machine, and I didn't want "Your Name " and "Your Mail" to pollute the history.

@cetincakiroglu cetincakiroglu added Status: Pending Review Issue or pull request is being reviewed by Core Team Status: Discussion Issue or pull request needs to be discussed by Core Team Resolution: Needs Issue An issue needs to be created for the pull request and removed Status: Pending Review Issue or pull request is being reviewed by Core Team Status: Discussion Issue or pull request needs to be discussed by Core Team labels May 3, 2024
@cetincakiroglu
Copy link
Contributor

Hi,

Could you please create an issue and link the PR with the issue?

@bjuergens
Copy link
Author

I can not create an issue (I think?). I can only report bugs. When I click the "feature request" button, I get redirected to the discussion page

grafik

@bjuergens
Copy link
Author

I completely missed the "open a blank issue" button, sorry.

I now made the issue, as requested: #15634

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Needs Issue An issue needs to be created for the pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants