Upon re-reading what I typed there, I want to clarify I mean marking it as
deprecated in 3.0, and actually removing the relevant flag/code in 4.0.
On Mar 20, 2023 at 9:44 AM -0600, Evan Rusackas <[email protected]>, wrote:
>
> I believe (5) can be re-proposed to accommodate… we heard other questions
> about this in the Town Hall, too, for what it’s worth. I believe marking the
> DASHBOARD_NATIVE_FILTERS flag as deprecated in the subsequent major version,
> along with relative code paths, and enabling your migration workflow (thank
> you!!!) would suffice for this 3.0 release. We can then remove the flag,
> force the migration, and clear other code paths as a change in 4.0.
