Skip to content

Conversation

@berry-13
Copy link
Collaborator

@berry-13 berry-13 commented Dec 1, 2025

Summary

This PR introduces a CONFIG_BYPASS_VALIDATION option that lets the app continue with defaults even when custom config validation fails. Validation errors now either trigger an explicit exit or fall back gracefully, and logging has been streamlined for clearer diagnostics.

LibreChat-AI/librechat.ai#456

Change Type

  • New feature (non-breaking change which adds functionality)
  • This change requires a documentation update

Testing

checked with both a correct and invalid librechat.yaml

Checklist

  • My code adheres to this project's style guidelines
  • I have performed a self-review of my own code
  • I have commented in any complex areas of my code
  • I have made pertinent documentation changes
  • My changes do not introduce new warnings
  • I have written tests demonstrating that my changes are effective or that my feature works
  • Local unit tests pass with my changes
  • Any changes dependent on mine have been merged and published in downstream modules.
  • A pull request for updating the documentation has been submitted.

@berry-13 berry-13 marked this pull request as ready for review December 1, 2025 15:13
@danny-avila danny-avila force-pushed the dev-staging branch 5 times, most recently from 79a02c8 to 8f35239 Compare December 2, 2025 18:14
@berry-13 berry-13 requested a review from danny-avila December 2, 2025 22:56
@danny-avila danny-avila force-pushed the dev-staging branch 2 times, most recently from d3aa6bb to 9ce9c71 Compare December 3, 2025 19:27
@danny-avila danny-avila merged commit 8a35d16 into dev-staging Dec 3, 2025
4 checks passed
@danny-avila danny-avila deleted the feat/exit-on-invalid-config branch December 3, 2025 22:23
danny-avila pushed a commit that referenced this pull request Dec 4, 2025
* fix: exit on invalid configuration and add bypass validation warning

* test: enhance loadCustomConfig tests for exit behavior on invalid config
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.

3 participants