Skip to content

fix(app): limit export filename length - #49143

Open
sdivyanshu90 wants to merge 1 commit into
anomalyco:devfrom
sdivyanshu90:limit-export-names
Open

sdivyanshu90 wants to merge 1 commit into
anomalyco:devfrom
sdivyanshu90:limit-export-names

Conversation

@sdivyanshu90

Copy link
Copy Markdown

Issue for this PR

Closes #49142

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

Caps the sanitized session title or slug at 250 ASCII characters before adding .json, keeping generated export filenames within a 255-byte component limit. Existing short filenames and the session-ID fallback remain unchanged.

How did you verify your code works?

Reproduced ENAMETOOLONG with the previous 305-byte result, added a regression test for a 300-character title, and ran the focused session-export test from packages/app: 6 tests passed with 7 assertions.

Screenshots / recordings

Not applicable; this is a non-UI filename-generation fix.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

@github-actions

Copy link
Copy Markdown
Contributor

The following comment was made by an LLM, it may be inaccurate:

The search found a related PR that should be reviewed:

Related PR:

This PR (#49138) also addresses export filename handling in the app, and was filed just before this one (#49143). While not an exact duplicate, these are closely related fixes to the export filename generation logic and should be reviewed together to ensure they don't conflict or duplicate effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Long session titles produce unsavable export filenames

1 participant