Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(media): add section resolving reference strings #1094

Merged
merged 1 commit into from
Dec 12, 2024

Conversation

hassiebp
Copy link
Contributor

@hassiebp hassiebp commented Dec 11, 2024

Important

Adds documentation for resolving media references in Langfuse and updates TypeScript configuration file.

  • Documentation:
    • Adds a section "Resolving Media References" in multi-modality.mdx explaining how to convert media references back to base64 data URI using resolve_media_references in Langfuse client.
    • Provides code examples in Python and JS/TS for resolving media references.
  • Configuration:
    • Removes next/navigation-types/compat/navigation reference from next-env.d.ts.
    • Updates URL in next-env.d.ts comment to correct path for TypeScript configuration documentation.

This description was created by Ellipsis for d6e2f60. It will automatically update as commits are pushed.

Copy link

vercel bot commented Dec 11, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
langfuse-docs ✅ Ready (Inspect) Visit Preview Dec 11, 2024 9:50pm

@dosubot dosubot bot added size:M This PR changes 30-99 lines, ignoring generated files. docs labels Dec 11, 2024

// NOTE: This file should not be edited
// see https://nextjs.org/docs/app/building-your-application/configuring/typescript for more information.
// see https://nextjs.org/docs/pages/building-your-application/configuring/typescript for more information.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The updated link seems incorrect. It should be https://nextjs.org/docs/app/building-your-application/configuring/typescript as per the Next.js documentation.

Copy link

📦 Next.js Bundle Analysis for langfuse-docs

This analysis was generated by the Next.js Bundle Analysis action. 🤖

One Page Changed Size

The following page changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load % of Budget (350 KB)
/docs/tracing-features/multi-modality 36.9 KB 370.4 KB 105.83% (🟡 +0.25%)
Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.

@hassiebp hassiebp merged commit aed55fe into main Dec 12, 2024
7 checks passed
@hassiebp hassiebp deleted the feat-add-media-replace-utility branch December 12, 2024 08:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs size:M This PR changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant