New data picker filter component

[gomonuk]

Hello!

The company I work for is very interested in adding a new, simpler data picker filter.

Could you please tell me what is the best way to do it? Can we add it without forking superset, as a plugin maybe? Can we prepare a merge request for you and add a new filter to the code base? It seems that the current filter is quite inconvenient, and there are already open threads about it.

[dosubot[bot]]

Hi @gomonuk! I'm Dosu and I’m helping the superset team.

You can add a new, simpler data picker filter to Superset by implementing it as a new filter plugin in the frontend codebase. Superset's filters (like Select, Range, and Time) are structured as modular plugins—each is a React component, typically extending ChartPlugin from @superset-ui/core, and lives in superset-frontend/src/filters/components example.

Currently, there isn't a fully supported way to add filter plugins purely as external npm packages without modifying the core codebase. While the architecture is plugin-like, new filters must be added directly to the codebase and exported, then integrated with the dashboard and explore views example. So, the best-supported approach is to prepare a merge request (pull request) with your new filter component for inclusion in the main repository.

When building your filter, follow the component guidelines: use Ant Design components where possible, style with Emotion and theme variables, write in TypeScript, and include Storybook stories and unit tests guidelines.

There are open threads discussing the inconvenience of the current filters and the need for better extensibility discussion. The maintainers are open to reviewing proposals for new, high-quality filter plugins.

If you need inspiration, check out the existing filter plugins like FilterSelectPlugin, RangeFilterPlugin, and TimeFilterPlugin for structure and integration patterns.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[gomonuk]

If a merge request is prepared, how long will it take to be added to the codebase?

[dosubot[bot]]

There’s no official timeline for how long it takes for a merge request to be reviewed and merged in Superset—it depends on factors like code quality, test coverage, scope, urgency, and reviewer availability. Recent frontend PRs (including filter component changes) have sometimes been merged within days, or even on the same day as their last update, if they’re well-scoped and high-priority example example.

For breaking changes, Superset uses a “breaking window” process that lasts about a month, during which maintainers focus on merging agreed breaking changes. Outside of this window, only non-breaking changes are accepted, and breaking changes are deferred to the next major release details.

To maximize your chances of a quick review and merge, make sure your PR follows the contribution guidelines, includes tests and documentation, and clearly explains the motivation and implementation.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[rusackas]

I think this PR is pretty close to what you want... if it's missing anything, weigh in there!
#44527