-
Notifications
You must be signed in to change notification settings - Fork 51
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
debug build for Maria #17
Comments
I like something like debug. I have had great success with opt in debug information by setting flags in localStorage. |
If a View template is parsed and has more than one top level element in the DOM fragment, then |
If a view is automatically instantiating a controller yet the controller file has not even been loaded then make a more specific error saying that particular controller constructor function cannot be found and include the expected controller name in the error message. |
If a view cannot locate a template (e.g. the template file is not loaded or the template is misnamed) then the error message is cryptic. Something about str is null when calling trim. |
The debugging builds are created and the messages mentioned in this ticket are implemented. The plan is to add more debugging messages over time as new message possibilities are discovered but everything in this ticket is completed. |
Could more development debugging statements be inserted in the Maria code to help developers? This code would be included in a built maria-debug.js but removed from maria.js and maria-min.js.
For example
Or embedded in another line
The build process in the Makefile will need to strip these debugging statements.
The text was updated successfully, but these errors were encountered: