Improve import messaging
Twintop opened this issue ยท 0 comments
Presently the import process does minimal sanity checking to ensure something of value can be imported by looking for core
table or a supported class.spec
table.
- Enhance this to strip out anything unsupported, e.g. other specs or garbage entries (just in case a bad faith actor is sharing strings).
- Only force a UI reload if the
core
table or the current class you're playing is being imported. - Give a secondary popup at least stating what specs (+core) will be imported and let them confirm.