While in the process of writing up a separate issue to submit for play-clj I've ran lein new play-clj dialog to form a new project where I can demonstrate the minimal code needed to reproduce issues with the dialog ui element.
As it turns out, this causes symbol conflicts if you name a project the same as any of the existing symbols defined in any of the namespaces in Play-CLJ.
In my case: Exception in thread "main" java.lang.IllegalStateException: dialog already refer s to: #'play-clj.ui/dialog in namespace: dialog.core, compiling:(dialog/core.clj :16:1)
This behavior makes sense. However, in the off chance that somebody insists on naming their project as something that's already defined elsewhere, perhaps there can be some name mangling to resolve the conflicts?
While in the process of writing up a separate issue to submit for play-clj I've ran
lein new play-clj dialog
to form a new project where I can demonstrate the minimal code needed to reproduce issues with the dialog ui element. As it turns out, this causes symbol conflicts if you name a project the same as any of the existing symbols defined in any of the namespaces in Play-CLJ. In my case:Exception in thread "main" java.lang.IllegalStateException: dialog already refer s to: #'play-clj.ui/dialog in namespace: dialog.core, compiling:(dialog/core.clj :16:1)
This behavior makes sense. However, in the off chance that somebody insists on naming their project as something that's already defined elsewhere, perhaps there can be some name mangling to resolve the conflicts?