> I find difficult to solve some recurring problems when developing my
> weblocks app. In particular, errors like 'odd number of &KEY arguments'.
This is an unpleasantness in SBCL (that is not particularly easy to fix
IIRC). Tracing sometimes helps.
> Unfortunately, I don't know how to face the problem directly, instead
> of trial-and-error, commenting-uncommenting blocks, etc., until I find
> out where the error is. I don't know even if I can get the stack trace
> somewhere (even in the 500 error page).
You can instruct Weblocks to enter the debugger when an error is
encountered. Recent -dev on SBCL will also print a backtrace when
a 500 occurs.
> So I'm wondering if there's a way to 'mock' the request and session, so
> that I can call (make-instance) on widget classes directly from the
> REPL. I know in weblocks-test there's a (with-request) macro, but I
> wasn't able to use it so far. Am I missing something?
I'm not sure. An out of the box IN-/WITH-{SESSION,REQUEST} is on
my TODO list. Until then:
Setting *session* is pretty easy. You can make Hunchentoot print
the sessions, write a function that gets the session object
belonging to a particular session number or id and then use that
for *session*.
With requests it's not that easy, but as you already have noticed
the test suite is able to give you mock request objects that you
can use to initialize *request* properly.
Why doesn't this work for you?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"weblocks" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---
