-
Notifications
You must be signed in to change notification settings - Fork 300
feat(calendar-view):Mobile-first supports the hidden time in schedule mode. #3408
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
Conversation
WalkthroughA conditional rendering directive was added to the event time display within the mobile-first calendar view component. The event time is now only shown when the Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant CalendarView
participant EventItem
User->>CalendarView: Render mobile-first view
CalendarView->>EventItem: Render event item
alt showTipTime is true
EventItem->>EventItem: Display event start/end time
else showTipTime is false
EventItem->>EventItem: Hide event time display
end
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
packages/vue/src/calendar-view/src/mobile-first.vueOops! Something went wrong! :( ESLint: 8.57.1 ESLint couldn't find the plugin "eslint-plugin-vue". (The package "eslint-plugin-vue" was not found when loaded as a Node module from the directory "".) It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
The plugin "eslint-plugin-vue" was referenced from the config file in ".eslintrc.js » @antfu/eslint-config » @antfu/eslint-config-vue". If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team. Tip ⚡️ Faster reviews with caching
Enjoy the performance boost—your workflow just got faster. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
⏰ Context from checks skipped due to timeout of 90000ms (1)
🔇 Additional comments (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Walkthrough此PR为日历视图组件引入了一个新功能,支持在移动优先的日程模式下隐藏时间显示。通过在时间显示的div元素上添加条件渲染属性 Changes
|
@@ -287,7 +287,7 @@ | |||
class="py-1.5 h-auto border border-color-border-separator rounded mb-2 shadow-sm" | |||
> | |||
<div class="px-1.5 mb-1.5 border-l-2 border-color-brand break-all">{{ event.title }}</div> | |||
<div class="mb-1.5 px-2 text-color-text-placeholder"> | |||
<div v-if="showTipTime" class="mb-1.5 px-2 text-color-text-placeholder"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The introduction of the v-if="showTipTime"
condition is a functional change that allows for the conditional display of event times. Ensure that showTipTime
is correctly managed in the component's data or computed properties to avoid any runtime errors.
WalkthroughThis PR introduces a new feature to the Calendar View component that supports hiding time display in mobile-first schedule mode. This function is achieved by adding the conditional rendering attribute Changes
|
PR
mobile-first支持日程模式隐藏时间
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information
Summary by CodeRabbit