Skip to content
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

Need for debug options #37

Open
ktym opened this issue Mar 9, 2015 · 1 comment
Open

Need for debug options #37

ktym opened this issue Mar 9, 2015 · 1 comment

Comments

@ktym
Copy link

ktym commented Mar 9, 2015

If there are no result rendered during the stanza development, it is hard to understand where the source of problem is. Therefore, it would be helpful if the "ts" command can support a debug mode which will show (maybe in console)

  • whether the template file is loaded successfully or not (stanza.render)
  • how the template file is compiled with variables
  • whether the query was executed or not (stanza.query) and the result
@darashi
Copy link
Contributor

darashi commented Mar 11, 2015

From v0.0.4, ts server builds stanzas that work in "development mode". It'll output the following information to console during stanza runtime:

  • query()
    • When entered query(). params are also logged.
    • The query actually rendered, that will be sent to SPARQL endpoint.
    • The endpoint to talk to.
    • Ajax results including the response itself.
  • render()
    • When entered render(). params are also logged.
    • The html fragment actually rendered.
    • The selector updated.

ts build builds stanzas that work in production mode as before. (The behavior can be overridden specifying -development=true/false option explicitly)

Implemented in dbb382a

Does this work as expected? Let me know if you have any suggestions 💡

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants