Inconsistent/unexpected naming (`Webauthn` vs `WebAuthn`) about webauthn-ruby

[bdewater]

I believe this is caused by the filename in your app as you mentioned. Zeitwerk is used to (re)load your Rails app code, not gems. From https://guides.rubyonrails.org/v7.0/autoloading_and_reloading_constants.html:

Idiomatic Rails applications only issue require calls to load stuff from their lib directory, the Ruby standard library, Ruby gems, etc. That is, anything that does not belong to their autoload paths, explained below.

Within an autoload path, file names must match the constants they define as documented here.
By default, the autoload paths of an application consist of all the subdirectories of app that exist when the application boots ---except for assets, javascript, and views--- plus the autoload paths of engines it might depend on.

[danielolivaresd]

Yeah, I also believe it had to do with my app's Webauthn module.

Even if I still feel that following a more standard naming convention (i.e. webauthn.rb declaring Webauthn and web_authn.rb declaring WebAuthn) could be clearer, it's not a huge thing, so feel free to close this issue if you want (I'm not closing it in case it is something you want to have in the roadmap or would accept a PR about).