Pedestal 0.5.3 is released

I’m new to Pedestal and finding this section on http://pedestal.io, Connecting to a Running Application (http://pedestal.io/guides/developing-at-the-repl#_connecting_to_a_running_application), a little empty-ish. Any recommendations on alternative tutorials? I’m not seeing much satisfactory via the Googles.

@schmudde I use emacs/cider with pedestal... works great.

@bherrmann - that’s what I’m doing, and I got through the rest of the tutorial, works great! But, when trying to use it with an existing codebase/running application, I’m having a little trouble. For example, do you ever use response-for?

@schmudde no, I've simply used ^C^C to reload the current expression, then I reload in the browser to see effects.

I’d love to point it at my localhost and get a response.

I see.

So you’re looking at the response in the browser.

yes.

exclusively.

Sometimes I’d like to get the response, and see the context in my REPL — so I can actually see how the data is structured (I didn’t write these data structures so I need some visibility). Any advice?

yes, I ocasionally test an expression from the repl, but typically something small like ... (camelcase-my-string "fluffy")

Its old school, put I just toss in a println/ppr on the function / and reload... then copy paste the output where i need it

What about testing what interceptors give back? You just test within the interceptor’s namespace?

That’s probably really what I’m asking. Interceptors often require context like user login. I’d love to deliver the context and see what data comes out the other side.

I'm pretty much a println wheel... take a look at my "check-auth-interceptor" https://github.com/bherrmann7/podcastmaker/blob/master/src/podcastmaker/service.clj

Super. Thank you, @bherrmann! All guidance is helpful at this point!

Is there any best practice on the project structure of a pedestal server that will ha a SPA client? Should they be in the same project and share project.clj since the client has no meaningful existence on its own or should they have their own projects for separation of concerns?

@zclj I match the team structure. If it’s one team, then I keep front end and back end in the same project. If it’s two teams, then two projects.