Skip to content
This repository was archived by the owner on Jan 2, 2025. It is now read-only.
This repository was archived by the owner on Jan 2, 2025. It is now read-only.

[Option] Some options changes should invalidate the container definition #10

@fancyweb

Description

@fancyweb

When some options are changed, the container definition should be invalidated.

Example :

  • I use the DisplayPrettyExceptionsAction with a logger.
  • The container definition gets cached.
  • I remove the logger from the options.
  • The cached container definition is used, but since the service exists the logger is expected in the options.

Or maybe we can be more lax in the check in the actions for those cases. It need to be checked carefully.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions