Why no Fog::AWS::Errors or Fog::Storage::Errors?

[Weston Platter]

I didn't see errors specifically for storage or AWS servivces here.
http://fog.io/1.0.0/rdoc/index.html#classes.

Is there a good reason for this?

[geemus (Wesley Beary)]

Good question.

There are really generic Fog::Errors which help in some cases and I'm not
sure anybody has ever really asked about more specific things. We
certainly could add increasingly specific errors, though I think I would
prefer to keep them at the storage level and share them than just have AWS
specific ones wherever possible. I guess nobody has really brought this up
specifically before.

Are there particular issues you are having related to this or features you
wish you could implement where this is a blocker?

Thanks!
wes

Post by Weston Platter
I didn't see errors specifically for storage or AWS servivces here.
http://fog.io/1.0.0/rdoc/index.html#classes.
Is there a good reason for this?

[Weston Platter]

Hi @geemus,

I wish I would have suscribed to the feed, I didn't see your response until
now.

No blocking issues. I am just implementing a *begin*/*rescue* block and
thought it would be nice to use Fog errors rather than reinvent the wheel.

I'll get a PR 1st draft together.

Post by geemus (Wesley Beary)
Good question.
There are really generic Fog::Errors which help in some cases and I'm not
sure anybody has ever really asked about more specific things. We
certainly could add increasingly specific errors, though I think I would
prefer to keep them at the storage level and share them than just have AWS
specific ones wherever possible. I guess nobody has really brought this up
specifically before.
Are there particular issues you are having related to this or features you
wish you could implement where this is a blocker?
Thanks!
wes

Post by Weston Platter
I didn't see errors specifically for storage or AWS servivces here.
http://fog.io/1.0.0/rdoc/index.html#classes.
Is there a good reason for this?

[geemus (Wesley Beary)]

Sounds good, let me know if you have questions or anything I can help with.
Thanks!

Post by Weston Platter
I wish I would have suscribed to the feed, I didn't see your response
until now.
No blocking issues. I am just implementing a *begin*/*rescue* block and
thought it would be nice to use Fog errors rather than reinvent the wheel.
I'll get a PR 1st draft together.

Post by geemus (Wesley Beary)
Good question.
There are really generic Fog::Errors which help in some cases and I'm not
sure anybody has ever really asked about more specific things. We
certainly could add increasingly specific errors, though I think I would
prefer to keep them at the storage level and share them than just have AWS
specific ones wherever possible. I guess nobody has really brought this up
specifically before.
Are there particular issues you are having related to this or features
you wish you could implement where this is a blocker?
Thanks!
wes

Post by Weston Platter
I didn't see errors specifically for storage or AWS servivces here.
http://fog.io/1.0.0/**rdoc/index.html#classes<http://fog.io/1.0.0/rdoc/index.html#classes>
.
Is there a good reason for this?

[Weston Platter]

Awesome. Will do.

Post by geemus (Wesley Beary)
Sounds good, let me know if you have questions or anything I can help
with. Thanks!

Post by Weston Platter
I wish I would have suscribed to the feed, I didn't see your response
until now.
No blocking issues. I am just implementing a *begin*/*rescue* block and
thought it would be nice to use Fog errors rather than reinvent the wheel.
I'll get a PR 1st draft together.

Post by geemus (Wesley Beary)
Good question.
There are really generic Fog::Errors which help in some cases and I'm
not sure anybody has ever really asked about more specific things. We
certainly could add increasingly specific errors, though I think I would
prefer to keep them at the storage level and share them than just have AWS
specific ones wherever possible. I guess nobody has really brought this up
specifically before.
Are there particular issues you are having related to this or features
you wish you could implement where this is a blocker?
Thanks!
wes

Post by Weston Platter
I didn't see errors specifically for storage or AWS servivces here.
http://fog.io/1.0.0/**rdoc/index.html#classes<http://fog.io/1.0.0/rdoc/index.html#classes>
.
Is there a good reason for this?