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
{{ message }}
This repository was archived by the owner on Mar 13, 2018. It is now read-only.
It is extremely difficult to debug core-ajax elements with bindings due to the fact that they simply d not fire when something is wrong with the url attribute. I propose that go() check for a truthy url and only proceed if it finds one.
Also, I realize that currently the function returns false when the go does not successfully activate the query. I think throwing an error would be more developer-friendly however. It would make problems obvious in the console and can be equivalent to the return value model using try/catch blocks.
It is extremely difficult to debug
core-ajaxelements with bindings due to the fact that they simply d not fire when something is wrong with the url attribute. I propose that go() check for a truthy url and only proceed if it finds one.Also, I realize that currently the function returns false when the go does not successfully activate the query. I think throwing an error would be more developer-friendly however. It would make problems obvious in the console and can be equivalent to the return value model using try/catch blocks.