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
from the instance.type.name? we might be able to get the component name.
This could be displayed to the user when an error occurs.
If the error occurs in a build in component ('UI'[upper case letter]) then we know it's used internally so we can go and test the parent by `instance.parent?.type?.name. We can display this, however if this again starts with the above pattern we should try to recursively find a parent with a name defined that isn't matching this pattern. This can slo be displayed as an approximation to tell where the issue originates from.
Scenarios to consider:
user imports the useVModel on it's own and uses it but an error occurs
user uses a UIInput component of which the parent is written by the user and it has name
user uses a UIInput component of which the parent is written by the user and it does not have a name
user uses a UIInput component inside a UIPanel component
The text was updated successfully, but these errors were encountered:
from the
instance.type.name?
we might be able to get the component name.This could be displayed to the user when an error occurs.
If the error occurs in a build in component (
'UI'[upper case letter]
) then we know it's used internally so we can go and test the parent by `instance.parent?.type?.name. We can display this, however if this again starts with the above pattern we should try to recursively find a parent with a name defined that isn't matching this pattern. This can slo be displayed as an approximation to tell where the issue originates from.Scenarios to consider:
useVModel
on it's own and uses it but an error occursThe text was updated successfully, but these errors were encountered: