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.
Hi there, we are currently having an issue with the initialization logic. As a
sendis used with the passed attributes, when some received attribute is not declared as an attribute accesor, aNoMethodErroris 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 criticalNoMethodErrors.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.