Skip to content

fix: allow Ash @global_opts authorize? to accept boolean or nil#2225

Merged
zachdaniel merged 1 commit intoash-project:mainfrom
chazwatkins:fix/2224
Jul 25, 2025
Merged

fix: allow Ash @global_opts authorize? to accept boolean or nil#2225
zachdaniel merged 1 commit intoash-project:mainfrom
chazwatkins:fix/2224

Conversation

@chazwatkins
Copy link
Copy Markdown
Contributor

  • Revert 7e34bbd change that updated Ash @global_opts authorize? to only accept boolean.

fixes #2224

All existing tests are passing

Contributor checklist

Leave anything that you believe does not apply unchecked.

  • I accept the AI Policy, or AI was not used in the creation of this PR.
  • Bug fixes include regression tests
  • Chores
  • Documentation changes
  • Features include unit/acceptance tests
  • Refactoring
  • Update dependencies

- Revert 7e34bbd change that  updated Ash @global_opts `authorize?` to only accept boolean.

fixes ash-project#2224
@chazwatkins
Copy link
Copy Markdown
Contributor Author

I wasn't able to reproduce the same error when not the providing authorize? option, but it did throw the error when explicitly setting authorize?: nil. Hopefully this fix will resolve the problem.

@zachdaniel zachdaniel merged commit ef34f00 into ash-project:main Jul 25, 2025
43 checks passed
@zachdaniel
Copy link
Copy Markdown
Contributor

🚀 Thank you for your contribution! 🚀

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.

Invalid value for :authorize? option: expected boolean, got: nil

2 participants