-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[#2528] Add categories to languages #2575
Conversation
955650d
to
369a7cb
Compare
|
||
return key; | ||
// Explicit categories (e.g. languages) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not clear to me how this differs from the above tool options where we search for an exact category match or a child match? Do we still need those, or are they covered by this new searchCategory
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For vehicle categories in tools, those are stored in separate configuration objects, while these are nested categories in a single object. The joys of years of legacy configuration data :).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it, thanks, that makes sense.
Groups languages into categories based on how they are defined in the SRD.
This change does modify the
languages
object in config, but it shouldn't be a breaking change for most cases because adding languages in the old fashion (CONFIG.DND5E.languages.test = "test";
) will still work correctly (those languages will just appear at the top level.Retrieving languages using
Trait.keyLabel
will also continue working. The only case that will lead to unexpected results is if code was retrieving languages directly (console.log(CONFIG.DND5E.languages.common
), but that will just return empty.