Compiling nickel v0.7.0 (file:///Users/matt/Documents/Projects/nickel.rs)
examples/chaining2.rs:9:5: 9:11 error: `server` does not live long enough
examples/chaining2.rs:9 server
^~~~~~
note: reference must be valid for the static lifetime...
examples/chaining2.rs:8:36: 18:2 note: ...but borrowed value is only valid for the block suffix following statement 0 at 8:35
examples/chaining2.rs: 8 let mut server = Nickel::new();
examples/chaining2.rs: 9 server
examples/chaining2.rs:10 .route("/")
examples/chaining2.rs:11 .get(middleware!("get"))
examples/chaining2.rs:12 .post(middleware!("post"))
examples/chaining2.rs:13 .put(middleware!("put"))
It only passed CI because I left that example out
I saw your comment on the PR btw. Thanks for the help. I'll take a look
<header>
</header>
<body>
<h4>{{title}}</h4>
<ul>
{{#basket}}
<li>
<b>Name:</b> {{{name}}}
</li>
{{/basket}}
</ul>
</body>
it simply gives me "Internal Server Error", and no messages on the console... is there a way to display the error detail?
@ruizander You can implement an error handler and print the error.message: See here for basic structure https://github.com/nickel-org/nickel.rs/blob/master/examples/example.rs#L115-L131
is there a way to read form post data from nickel request object? I have seen the example with reading the request body into a string but that does not gives me individual form element values
if reading the request data into a hashmap does not exist, then I will write my own
In case such a method does not already exist please take a look at this http://is.gd/HtbeqW, since nickel already uses the crate url there is no new dependency for this code, and the request object in function parameters can be replacesd by &self when you put it in the nickel::Request object
nickel is already using the url crate for parsing url query string, since the nature of data in querystring and in form post is same we can use same method for both cases
I could have created a pull request but I wasn't sure if nickel already have a method for geting post form data into a hashmap
in case it doesn't have such a method, I will create a pull request
@masoodahm You might want to add to the discussion here (and also check the linked implementation): https://github.com/nickel-org/nickel.rs/issues/240#issuecomment-145459986
@ruizander add
RUST_BACKTRACE=1 before your command, e.g. RUST_BACKTRACE=1 cargo test
Do you have a link available for 'javascript domains', I'm not really sure what that means?
@Ryman I mean exceptions in c++/java way... here is a good link about this subject: https://www.joyent.com/developers/node/design/errors
considering this article, I mean "operational errors"
@Ryman here is another good article: https://engineering.gosquared.com/error-handling-using-domains-node-js
It looks like in general this is talking about unchecked exceptions, which rust doesn't have, we have panic, but that should only be used in extreme cases (often highlighting a bug). In the case of panic the thread currently dies (we would need to wait for catch_panic to stabilize to allow custom behaviour here)
@ruizander @Ryman It seems to me that the idiom for dealing with operational errors is just different. Javascript operations that may fail take a callback of the form
function (err, res) {...} and rust operations should return a result type that you can match against. match res {
Ok(v) => // do something with v,
Err(err) => // handler err
}
@mattbanister Pretty much yeah, for 'operational errors' you'll want to do the same as the linked article, handle it, or propagate the type. In nickel you may also want to use
try_with!, as seen in an old example here: https://github.com/Ryman/nickel-todo-backend/blob/master/src/main.rs#L77
@ruizander If you have a more concrete example of what you want to handle, I can take a look :)
Off topic but I went to a meetup about this project last night : http://maidsafe.net/. Ambitious project (it basically aims to be a replacement for the internet) and their entire codebase is rust.
Also interesting that all of their code has been rewritten in rust
@ruizander Well, depends on how your database code deals with things :P But currently, the two that I know of
nickel-sqlite and nickel-postgres will panic due to unwraps, which should 500 but doesn't (see hyperium/hyper#676 as a proposed fix for handling panics better in hyper). You can implement this behavior yourself with a frontloaded Middleware which sets the default StatusCode to 500 or whatever you need, and that will be used if things panic.
@lorenz Yes! The doc mentions how to create a
NickelError here: http://docs.nickel.rs/nickel/struct.NickelError.html. The examples show how to register custom handlers for different error codes: https://github.com/nickel-org/nickel.rs/blob/master/examples/example.rs#L127. Is that what you wanted to do?
I was trying to understand when to use str / String, and I've noticed &'a str a lot, but I don't get it..
@ruizander Is there something that feels particularly confusing about lifetimes?
@ruizander Regarding
String/&str, you generally want to use &str, simply because you can create a &str cheaply from a String, but not the other way around.