Exception::Class was not removed completly #5
Comments
|
Oops... It should be replaced. Thanks for the heads-up |
|
@jplesnik I'd like to know how you found this issue. Was it by reading code or did you get an error ? All the best |
|
I was updating Fedora package to the latest version. Before I removed Exception::Class from build-requires, I just checked via grep if Exception::Class is no using in code. |
|
Interesting. I did not know that Config::Model was now up-to-date on Fedora. That's very good news. 😃 I'll fix this issue asap (I need to check whether this code is dead or not). BTW, feel free to ask for changes that may ease your work as Fedora packager (As Debian packager, I know that upstream can help a lot in our day-to-day activities) All the best |
dod38fr
added a commit
that referenced
this issue
Feb 12, 2016
YAML backend changes:
* Remove YAML file when no data is left
* When a root class has only one element, the backend
write (and read) only the content of that element (this
reduce the depth of the written data structure by one).
Functional improvements:
* Added "ChangeTracker" log class and traces (Log::Log4Perl)
* HashId: load_data can load ordered data in non-ordered hash
Bug fixes:
* Removed Exception::Class from warper error handler
(gh #5, Thanks jplesnik)
* Dumper/Loader: handle literal \\n
|
Fixed in v2.079 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Exception::Class is still used in Config::Model::Warper
lib/Config/Model/Warper.pm:L569: if ( my $e = Exception::Class->caught($expected_error) ) {Is it correct or should it be replaced?
The text was updated successfully, but these errors were encountered: