Skip to content

Conversation

unused
Copy link

@unused unused commented Jun 30, 2025

Using a top_namespace in configuration that is a symbol fails with further processing where a string is expected. Relying on a conversion in settings constructor prevents an unexpected error.

What error is happening?

Given a symbol is used for top_namespace, it results in the following error:

Namespaced messages with top namespace allows symbol for top namespace
     Failure/Error: data.transform_keys { _1.gsub(DEFAULT_MESSAGES_ROOT, config.top_namespace) }

     TypeError:
       no implicit conversion of Symbol into String

@unused unused force-pushed the fix-top-namespace-as-symbol branch from 3f9e8af to c525a28 Compare June 30, 2025 20:11
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