-
Notifications
You must be signed in to change notification settings - Fork 3k
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]日期筛选组件可设置查询的起始日期 #6005
Comments
感谢反馈。 有查询按钮的时候,默认加载全部数据,点查询后才查询需要日期或日期取件的数据
没有查询按钮的时候,虽然默认显示所设置日期或日期取件的数据,但是点清除时间按钮后缺默认加载全部数据
自定义时间范围短期内还没有支持计划。 |
dataeaseShu
added a commit
that referenced
this issue
Mar 12, 2024
dataeaseShu
added a commit
that referenced
this issue
Mar 12, 2024
feat(查询组件): 日期筛选组件可设置查询的起始日期 #6005
dataeaseShu
added a commit
that referenced
this issue
Mar 13, 2024
dataeaseShu
added a commit
that referenced
this issue
Mar 13, 2024
feat(查询组件): 日期筛选组件可设置查询的起始日期 #6005
dataeaseShu
added a commit
that referenced
this issue
Mar 18, 2024
dataeaseShu
added a commit
that referenced
this issue
Mar 18, 2024
feat(过滤组件): 日期筛选组件可设置查询的起始日期 #6005
dataeaseShu
added a commit
that referenced
this issue
Mar 19, 2024
dataeaseShu
added a commit
that referenced
this issue
Mar 19, 2024
feat(过滤组件): 日期筛选组件可设置查询的起始日期 #6005
dataeaseShu
added a commit
that referenced
this issue
Mar 19, 2024
dataeaseShu
added a commit
that referenced
this issue
Mar 19, 2024
feat(查询组件): 日期查询组件可设置查询的起始日期 #6005
dataeaseShu
added a commit
that referenced
this issue
Mar 20, 2024
dataeaseShu
added a commit
that referenced
this issue
Mar 20, 2024
fix(过滤组件): 日期筛选组件可设置查询的起始日期 #6005
dataeaseShu
added a commit
that referenced
this issue
Mar 20, 2024
dataeaseShu
added a commit
that referenced
this issue
Mar 20, 2024
feat(查询组件): 日期筛选组件可设置查询的起始日期 #6005
新版本已处理,请更新版本。 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
日期筛选组件在现有的功能上新增可以查询的起始日期,或自定义“最近3个月”“最近半年”“最近1年”,超过以上时间的自定义提示文案。
原因是现有的功能:有查询按钮的时候,默认加载全部数据,点查询后才查询需要日期或日期取件的数据
没有查询按钮的时候,虽然默认显示所设置日期或日期取件的数据,但是点清除时间按钮后缺默认加载全部数据。
The text was updated successfully, but these errors were encountered: