the decision whether or not to overwrite an existing schema is up to the user#7
the decision whether or not to overwrite an existing schema is up to the user#7dimtrovich wants to merge 1 commit intothephpleague:mainfrom
Conversation
|
The code itself looks fine, but I'm not sure I understand the use case here. Would you mind describing why you'd want this to ignore an added schema? And with that use case, would it be better to have an |
|
by default, the configuration is initialized with a schema array. it can happen that we add by mistake a new schema having the key of an already existing schema, by offering the possibility to the developer not to overwrite a schema, we are sure that the values returned will actually correspond to the first schema defined |
|
I work on an internal micro framework, the configurations are in files and we add the schemas only when we try to recover a configuration (this allows not to load the unused schema and saves time) the fact is that there are certain predefined patterns that should not be modified, hence this idea |
No description provided.