Skip to content

Conversation

@agoose77
Copy link
Contributor

Addresses #2405

@changeset-bot
Copy link

changeset-bot bot commented Nov 10, 2025

⚠️ No Changeset found

Latest commit: 4e8869e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@agoose77 agoose77 marked this pull request as draft November 10, 2025 12:13
@github-actions github-actions bot added the enhancement New feature or request label Nov 10, 2025
@agoose77
Copy link
Contributor Author

Working on this PR surfaced something I've noticed implicitly — our story for error handling (and probably the TUI more generally) could benefit with being clearer.

e.g. we have

  • fileWarn for pure transforms
  • session.log and addWarningForFile for session transforms
  • thrown exceptions

In general, the core of MyST should be very tolerant to errors and warn where possible. But there are things like "broken config" that aren't really ignorable. We need a nicer way to handle such situations and early exit

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

Labels

enhancement New feature or request

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants