Am 01.01.20 um 15:04 schrieb Adam Johnson:
>
>     This seems a weird suggest, but when apps depend on another app it
>     should be able to override settings for that dependency too
>     (because it "uses" that app anyway).
>
>
> It does seem weird to suggest. I haven't seen such a use case myself.
> Can you describe in more detail?
>
> For me, I can only imagine it would violate the "principle of least
> astonishment" that if I had app A installed for some time, then
> installed app B on top, app B would change the default or manually
> configured settings of app A. I would prefer if app B complained (via
> system check) that I had an incompatible app A configuration.
>
Maybe you're right. I was about to answer how the system should behave
when not thinking in "apps" - which are in a flat hierarchy. In GDAPS I
try to think in modules/plugins of ONE application - that's what I try
to achieve. Let's explain shortly: My main aim is to create an Open
Source Electronic Medical Record - meaning I want to create a base
system where maybe 3rd party companies could add their own plugins to
the system. Everything based upon django as backend (with a
REST/Graphene web API), and variable frontends, let's say a web frontend
with Vue.js.

But even when a base module has some "default settings", and I install a
module B which overrides that defaults because system behaviour is
different when using this module, it doesn't make sense. Such a case
should be done in code (module B circumvents the default settings etc.)
- but settings merging / hierarchy maybe isn't the best way to go. I
also strictly believe in "namespaces are a good thing."

So forget overriding settings, there only remains the easy settings
access via one object, which would be great.

Christian

-- 
Dr. Christian González
https://nerdocs.at

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/88ae1ed1-425d-1f8c-aef6-6062e9b7caf3%40nerdocs.at.

Attachment: pEpkey.asc
Description: application/pgp-keys

Reply via email to