reactjs

相关平台

钉钉小程序

使用框架: React

复现步骤

3.4版本升级至3.5

期望结果

升级成功

实际结果

升级失败

环境信息

👽 Taro v3.5.0-beta.0


  Taro CLI 3.5.0-beta.0 environment info:
    System:
      OS: Windows 10
    Binaries:
      Node: 16.14.0 - D:\Program Files\nodejs\node.EXE
      Yarn: 1.22.17 - C:\Users\caiju\AppData\Roamin

Is your feature request related to a problem? Please describe.

Since the new v4 major release of react-admin, it seems we have persisted filter enabled by default.

This is convenient for the navigation. However, sometimes we need to reset to the defaults and we may have a lot of filter to disabled one by one.

Describe the solution you'd like

A generic "Clear filter" action that

Replaced image with widget's video

What do you want and why?

I want an exported getQueryData function that takes in a resolver.

Instead of having to get the query key manually, such as below

const queryKey = getQueryKey(getTasks, { taskListId })
const tasks = queryClient.getQueryData<PromiseReturnType<typeof getTasks>>(queryKey)

I want to be able to write

const tasks = getQueryData(getTasks, { 

Please confirm the following

• I agree to follow this project's code of conduct.
• I have checked the current issues for duplicates.
• I understand that AWX is open source software provided for free and that I might not receive a timely response.

Feature Su

Issue Type (check one)

• Bug Report

Description (type any text below) -->

When tabbing through the Spectrum interface it's difficult to know what you're interacting with since the outlines for tabbable elements have been removed.

If you force outlines back on you can see what is being tabbed.

*:focus {
    outline: 3px solid orange !important;
    outline-offse

We should audit all our prod deps for actual usage. Discovered today that we're not using:

• marksy: https://github.com/FormidableLabs/spectacle/search?q=marksy

The current overview section in the application detail page has 4 charts which need to move from promQL to query-builder APIs. Below are the charts on that page:

1. Application latency
2. Requests
3. Error Percentage
4. Top Endpoints