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

Move date-range-picker to Top for Logbook and History #22947

Open
wants to merge 3 commits into
base: dev
Choose a base branch
from

Conversation

boern99
Copy link
Contributor

@boern99 boern99 commented Nov 21, 2024

Breaking change

Proposed change

This is an missing Style-Improvement for bed470f
@wendevlin: referring your discussion: #22802 (comment)

Displays Prev. and Next buttons also on mobiles.
Similar to the Energy Dashboard, selecting the date in the header area offers added value, especially on mobile devices.
image

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New feature (thank you!)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Example configuration

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue or discussion:
  • Link to documentation pull request:

Checklist

  • The code change is tested and works locally.
  • There is no commented out code in this PR.
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

Copy link
Contributor

coderabbitai bot commented Nov 21, 2024

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@wendevlin
Copy link
Contributor

@boern99 can you add a mobile screenshot too please?

@wendevlin wendevlin added the Needs UX Pull requests requiring a review from the Home Assistant design team label Nov 21, 2024
@boern99
Copy link
Contributor Author

boern99 commented Nov 21, 2024

@boern99 can you add a mobile screenshot too please?

image

@bramkragten
Copy link
Member

Why not use a shorter format for the date like we do on the energy dashboard?

image

@bramkragten
Copy link
Member

In your mobile screenshot I miss the button to select a date?

@boern99
Copy link
Contributor Author

boern99 commented Nov 21, 2024

In your mobile screenshot I miss the button to select a date?

can be selected by clicking on the date

@boern99
Copy link
Contributor Author

boern99 commented Nov 21, 2024

Why not use a shorter format for the date like we do on the energy dashboard?

image

used the date format from the actual code, including the time. In Energy Dashboard there is no time.

@boern99
Copy link
Contributor Author

boern99 commented Nov 22, 2024

should i use a shorter Date Format? But when i leave the time Information: it would need more space than in Energy Dashboard: 2 Lines for start and end date as in this PR? Leave the Dateselector until there is no space left? Would it be better to hide the Date and leave the Dateselector? If you like to change the code feel free to make a Suggestion.

@wendevlin
Copy link
Contributor

It's a good idea, but we have to discuss this with the UX team.
I don't like that the time is seperated from the target picker, moreover you don't see that it is about from - to timerange.

I am pretty sure we can get an awesome design to improve this selector, it is possible that it can take some time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-signed Needs UX Pull requests requiring a review from the Home Assistant design team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants