-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access NSError Object in ErrorView #7
Comments
Hi, thanks for the suggestion. I was thinking about a generic
Optionally, the current state (including any errors) might be passed with these calls. |
Yes, that would be sufficient. |
Perfect. 👍 Regarding your question: A quick solution would be to use a transparent view as one of your placeholder views. However, this will block the UI behind it. Alternatively, we could look into the possibility to provide a delegate method (on the view or the controller) to return the constraints for specific views. |
Any updates on exposing the NSError object inside the error view? I would really like to give a better explanation to the user why the operation failed, instead of a generic message. |
In order to give the user a more concrete info than just "Something went wrong.", it would be straightforward to have access to the NSError object in the view.
The text was updated successfully, but these errors were encountered: