Compliance Issue - Non EE packages depend on EE components

[jhodges-gh]

Hi,

This issue is similar, but not equivalent to: #1896

There are several instances where non-ee packages have dependencies to Enterprise Edition components. This puts users who are using the Community Edition in a rough spot when it comes to licensing.

1. Is this intentional? The DateRange Selector/Picker feels like it should be included in the Community Edition
2. What are the official recommendations for using the Community edition? Would the steps be to fork the repo, and then delete the "ee" folders?

Here are some examples:

• onyx/web/src/lib/search/utils.ts

  Line 3 in 420d261

  import { DateRangePickerValue } from "@/app/ee/admin/performance/DateRangeSelector";

• onyx/web/src/components/filters/SourceSelector.tsx

  Line 15 in 420d261

  import { DateRangePickerValue } from "@/app/ee/admin/performance/DateRangeSelector";

• onyx/web/src/lib/search/interfaces.ts

  Line 1 in 420d261

  import { DateRangePickerValue } from "@/app/ee/admin/performance/DateRangeSelector";

[Weves]

@jhodges-gh really appreciate the heads up. We'll make sure we address this this week.

To all Community Edition users: you have my word (as one of the maintainers / founders) that you are completely good to go with using the project — the intent is 100% to have the Community Edition as a MIT licensed project.

I understand this likely will not appease folks in compliance, but just wanted to put that out there for what its worth.