mirror of
https://github.com/hanzo-apps/dataroom.git
synced 2026-10-30 14:47:36 +00:00
zeekayandHanzo Dev
f77d5010d8
Papermark dual-licenses: AGPL-3.0 for the tree, a separate commercial
licence for ee/. We hold the first and not the second, so none of the
second may live here.
ee/ was already absent from main, but it was never deleted. 98f0da7fa
("ci: amd64-only build") renamed 150 files out of ee/ byte-identical
into features/, lib/billing/legacy/ (ee/stripe), lib/billing/limits/
(ee/limits), and flattened app/(ee)/ into app/ — putting commercially
licensed code under our AGPL root LICENSE. A rename is not a deletion.
Every path that commit moved is now gone, edited-since or not.
Deleted, with their routes and UI entry points: features/ai and
app/api/ai, features/workflows and app/api/{workflows,workflow-entry},
features/conversations and the Q&A/FAQ surface, features/security/sso
with app/api/auth/saml + app/api/scim + lib/jackson.ts (we use Hanzo
IAM OIDC natively), features/dataroom-invitations, features/templates,
features/access-notifications, features/conversions, features/
permissions. Five of these were gated by lib/featureFlags, which reads
@vercel/edge-config and returns false for every flag when EDGE_CONFIG
is unset — every non-Vercel deployment we run. Those flags are gone too.
Deleted the commercial gating outright rather than reimplementing it:
lib/billing/legacy (ee/stripe) and lib/billing/limits (ee/limits), the
upgrade modals and banners, UpgradeButton, FeaturePreview, PlanBadge,
the trial and blocking modals, /settings/upgrade, /settings/billing and
the billing checkout/seat/pause/cancel API. usePlan() no longer returns
capability booleans — the plan tag describes provisioning, it is not a
permission — and useLimits() is gone with every quota check it fed.
Subscription pause went the same way. Also dropped the npm dependencies
that existed only for the removed features (@boxyhq/saml-jackson, the
@ai-sdk packages, openai, streamdown, use-stick-to-bottom,
@trigger.dev/python) and the Jackson-specific next.config webpack shims.
Rewritten as original Hanzo code where a capability was load-bearing:
- lib/utils/get-file-size-limits.ts — one UPLOAD_LIMITS set plus
getFileSizeLimit(contentType), env-overridable. Operational limits,
not commercial ones, so the tus and browser-upload paths still refuse
oversized files without consulting a plan matrix.
- components/links/link-sheet/permissions-sheet.tsx — a flat, depth
annotated item list with view/download switches over the same
/permission-groups API. Two states, not three. ItemPermission now has
a single definition in lib/types.ts.
- app/api/links/[id]/upload/route.ts — visitor uploads, built around one
authorize() helper shared by GET and POST, and a notification debounce
keyed per (link, viewer) instead of listing and cancelling runs.
There is now exactly one link sheet: the ee DataroomLinkSheet duplicated
the AGPL LinkSheet, which already handled DATAROOM_LINK. Replaced
upstream's Omit<LinkType, "WORKFLOW_LINK"> — Omit on a string union
yields an object type and never narrowed anything — with a real union.
Verified: the S3/tus upload+download harness passes 13/13 against MinIO
after the deletions, and tsc goes from 257 pre-existing errors on
origin/main to 192 with zero files worse than baseline.
Reasoning recorded in LLM.md. LICENSE untouched.
Co-authored-by: Hanzo Dev <[email protected]>
110 lines
2.7 KiB
TypeScript
110 lines
2.7 KiB
TypeScript
"use client";
|
|
|
|
import Link from "next/link";
|
|
import { useRouter } from "next/router";
|
|
|
|
import * as React from "react";
|
|
|
|
import { cn } from "@/lib/utils";
|
|
|
|
import { Separator } from "@/components/ui/separator";
|
|
|
|
type Props = {
|
|
navigation: {
|
|
label: string;
|
|
href: string;
|
|
segment: string | null;
|
|
tag?: string;
|
|
disabled?: boolean;
|
|
}[];
|
|
className?: string;
|
|
};
|
|
|
|
export const NavMenu: React.FC<React.PropsWithChildren<Props>> = ({
|
|
navigation,
|
|
className,
|
|
}) => {
|
|
return (
|
|
<nav
|
|
className={cn("sticky top-0 bg-background dark:bg-gray-900", className)}
|
|
>
|
|
<div className="flex w-full items-center overflow-x-auto px-4 pl-1">
|
|
<ul className="flex flex-row gap-4">
|
|
{navigation.map(({ label, href, segment, tag, disabled }) => (
|
|
<NavItem
|
|
key={label}
|
|
label={label}
|
|
href={href}
|
|
segment={segment}
|
|
tag={tag}
|
|
disabled={disabled}
|
|
/>
|
|
))}
|
|
</ul>
|
|
</div>
|
|
<Separator />
|
|
</nav>
|
|
);
|
|
};
|
|
|
|
const NavItem: React.FC<Props["navigation"][0]> = ({
|
|
label,
|
|
href,
|
|
segment,
|
|
tag,
|
|
disabled,
|
|
}) => {
|
|
const router = useRouter();
|
|
// active is true if the segment included in the pathname, but not if it's the root pathname. unless the segment is the root pathname.
|
|
let active =
|
|
router.pathname.includes(segment as string) &&
|
|
segment !== "/datarooms/[id]";
|
|
|
|
if (segment === "/datarooms/[id]") {
|
|
active = router.pathname === "/datarooms/[id]";
|
|
}
|
|
|
|
// Special case for permissions - also active when pathname includes "groups"
|
|
// but NOT when it's within settings (like settings/file-permissions)
|
|
if (segment === "permissions") {
|
|
active =
|
|
(router.pathname.includes("permissions") &&
|
|
!router.pathname.includes("settings")) ||
|
|
router.pathname.includes("groups");
|
|
}
|
|
|
|
if (segment === "analytics" && router.pathname.includes("groups")) {
|
|
active = false;
|
|
}
|
|
|
|
return (
|
|
<li
|
|
key={label}
|
|
className={cn(
|
|
"flex shrink-0 list-none border-b-2 border-transparent p-2",
|
|
{
|
|
"border-primary": active,
|
|
hidden: disabled,
|
|
},
|
|
)}
|
|
>
|
|
<Link
|
|
href={href}
|
|
className={cn(
|
|
"text-content-subtle hover:bg-background-subtle -mx-3 flex items-center gap-1 rounded-lg px-3 py-2 text-sm font-medium hover:bg-muted hover:text-primary",
|
|
{
|
|
"text-primary": active,
|
|
},
|
|
)}
|
|
>
|
|
{label}
|
|
{tag ? (
|
|
<div className="text-content-subtle rounded border bg-background px-1 py-0.5 font-mono text-xs">
|
|
{tag}
|
|
</div>
|
|
) : null}
|
|
</Link>
|
|
</li>
|
|
);
|
|
};
|