As of version 0.3.0 (see #30) DataLayer classes are checked for existence via basic string comparison, implying that custom DataLayer classes need to be directly added to the LocusZoom singleton. This could create conflicts in the future as implementers of the plugin overwrite existing attributes of the singleton.
Proposed Solution
As described by @mflick here this could be more effectively handled with a custom collection class here with add/get/set methods pattern as seen elsewhere in the plugin.
The Problem
As of version 0.3.0 (see #30) DataLayer classes are checked for existence via basic string comparison, implying that custom DataLayer classes need to be directly added to the
LocusZoom
singleton. This could create conflicts in the future as implementers of the plugin overwrite existing attributes of the singleton.Proposed Solution
As described by @mflick here this could be more effectively handled with a custom collection class here with add/get/set methods pattern as seen elsewhere in the plugin.