Bug #1064

Non-existing configuration options should throw an exception

Added by Karsten Dambekalns over 13 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Should have
Assignee:
Category:
Configuration
Target version:
-
Start date:
2008-07-15
Due date:
% Done:

100%

Estimated time:
0.50 h
PHP Version:
Has patch:
Complexity:

Description

When accessing an option in a configuration container that has not been set (i.e. does not exist) an exception should be thrown. Currently an object is returned in all cases; if using that it may have unexpected results due to automatic typecasting in PHP (e.g. it evaluates to TRUE if used as boolean).

If an exception would be thrown the typo or missing configuration would be visible immediately.

#1

Updated by Robert Lemke over 13 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Applied in changeset r1034.

#2

Updated by Robert Lemke over 13 years ago

  • Status changed from Resolved to Accepted
  • Assignee set to Robert Lemke
  • % Done changed from 100 to 50

The configuration manager only locks the container on the first level - the container does not recursively lock its sub containers!

#3

Updated by Robert Lemke over 13 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 50 to 100

Applied in changeset r1080.

Also available in: Atom PDF