You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, we are currently having an issue with the initialization logic. As a send is used with the passed attributes, when some received attribute is not declared as an attribute accesor, a NoMethodError is raised. This used to be fine, but as the application in which wi use Scrivener grew, this errors became more common and started masking really critical NoMethodErrors.
It would be great if a configuration could be introduced to raise a custom Scrivener exception instead of the generic one.
I wouldn't mind iterating a PR if a mantainer validates this approach.
The text was updated successfully, but these errors were encountered:
Hi there, we are currently having an issue with the initialization logic. As a
send
is used with the passed attributes, when some received attribute is not declared as an attribute accesor, aNoMethodError
is raised. This used to be fine, but as the application in which wi use Scrivener grew, this errors became more common and started masking really criticalNoMethodError
s.It would be great if a configuration could be introduced to raise a custom Scrivener exception instead of the generic one.
I wouldn't mind iterating a PR if a mantainer validates this approach.
The text was updated successfully, but these errors were encountered: