Skip to content

Conversation

@henriquemoody
Copy link
Member

There's more value on showing how assert() displays the validation messages than simply showing if isValid() returns true or false.

However, that increases the chances of having outdated documentation, so I created a console command that updates the Markdown files with the correct message.

@codecov
Copy link

codecov bot commented Jan 8, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.43%. Comparing base (6022914) to head (98cd28f).

Additional details and impacted files
@@            Coverage Diff            @@
##               main    #1596   +/-   ##
=========================================
  Coverage     97.43%   97.43%           
  Complexity      981      981           
=========================================
  Files           211      211           
  Lines          2259     2259           
=========================================
  Hits           2201     2201           
  Misses           58       58           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@henriquemoody henriquemoody force-pushed the docs/assert branch 8 times, most recently from 5d8119a to d4d70ce Compare January 10, 2026 05:29
There's more value on showing how `assert()` displays the validation
messages than simply showing if `isValid()` returns `true` or `false`.

However, that increases the chances of having outdated documentation, so
I created a console command that updates the Markdown files with the
correct message.
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.

1 participant