Development

#7673 (Specifying a non-existant plugin to not enable should not throw an exception)

You must first sign up to be able to contribute.

Ticket #7673 (closed defect: wontfix)

Opened 3 months ago

Last modified 3 months ago

Specifying a non-existant plugin to not enable should not throw an exception

Reported by: Kris.Wallsmith Assigned to: Kris.Wallsmith
Priority: minor Milestone:
Component: configuration Version: 1.3.x DEV
Keywords: Cc:
Qualification: Unreviewed

Description

As reported here, if a plugin that does not exist is specified as one that should not be enabled, symfony currently throws an exception. It makes sense to me that this not throw an exception, similar to how unset() does not complain if you unset something that isn't set in the first place.

Change History

11/23/09 13:39:09 changed by fabien

... except that if you have a typo in the plugin name, you won't notice easily. The exception gives you immediate feedback in such a case.

11/23/09 13:42:38 changed by FabianLange

I disagree, because we want to alert developers when they make mistakes. I would rather say that there needs to be an upgrade from 1.3 to 1.4

11/23/09 15:23:59 changed by Kris.Wallsmith

  • status changed from new to closed.
  • resolution set to wontfix.
  • milestone deleted.

The Sensio Labs Network

Since 1998, Sensio Labs has been promoting the Open-Source software movement by providing quality web application development, training, consulting.
Sensio Labs also supports several large Open-Source projects.

Open-Source Products

Services

> More