Skip to content
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

[BUG] Conflicts with kanka-Foundry #717

Open
eXaminator opened this issue Sep 6, 2024 · 2 comments
Open

[BUG] Conflicts with kanka-Foundry #717

eXaminator opened this issue Sep 6, 2024 · 2 comments

Comments

@eXaminator
Copy link

eXaminator commented Sep 6, 2024

Hi, I'm the maintainer of the Kanka-Foundry module (https://github.com/eXaminator/kanka-foundry).

I received a conflict bug (eXaminator/kanka-foundry#140) but was able to trace it back to your module.

It seems that you - for some reason - make a copy of foundries JournalEntryPage dataTypes using foundry.utils.mergeObject(). The problem here is, that this function seems to handle object property keys with points in them (like kanka-foundry.abilities) by creating nested objects (like { 'kanka-foundry': { 'abilities': ... } }). Once this happens, it breaks other stuff in foundry down the line as foundry expects dataTypes to be a simple (flat) key-value map of schemas.

Here's the line:

CONFIG.JournalEntryPage.dataModels = foundry.utils.mergeObject((CONFIG.JournalEntryPage.dataModels || {}), {});

Is there a specific reason for this call? Could it be done another way as to prevent breaking other modules that use dots no namespace their dataType names?

Thanks!

@Nedrapter
Copy link

I've been a victim of this conflict and it makes the world not able to load anymore! Please fix! I love both modules!

@eXaminator
Copy link
Author

Given that there seem to be at least 3 instances of this bug creeping up by now and the issue has had the "fixed waiting release" tag for over 2 months now, is there something specific blocking this release? Seeing as this is a bug actually blocking people from even entering their world without safe mode it would be great if a fix for this could be released :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants