Test your Rocket Contrib knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
Why might a smaller framework ecosystem (like Rocket's, compared to a much larger framework like Rails or Django) rely more heavily on a small number of officially-maintained contrib integrations, rather than a vast third-party plugin marketplace?
In this round
Why might a smaller framework ecosystem (like Rocket's, compared to a much larger framework like Rails or Django) rely more heavily on a small number of officially-maintained contrib integrations, rather than a vast third-party plugin marketplace?
What is a practical reason a developer reading an older Rust web development tutorial referencing `rocket_contrib::json::Json` might need to adjust that code for a current Rocket project?
What is a reasonable general practice for a team maintaining a codebase that depends on rocket_contrib, when considering whether to migrate to a newer version of Rocket where some of that functionality has moved into the core crate?
Why might a web framework like Rocket keep certain features (JSON handling, database pooling, templating) in a separate "contrib" crate rather than bundling them directly into the core framework?
Why is it common for a young or evolving web framework to initially separate optional integrations (like Rocket Contrib) from a minimal, stable core, only later folding some of them into core as the framework matures?
Why might a developer new to Rocket specifically look up whether a piece of desired functionality (like database pooling) lives in Rocket's core crate or requires an additional dependency, before starting a new project?
What is a practical reason a Rocket project handling both JSON APIs and server-rendered HTML pages might need multiple Rocket Contrib (or equivalent) integrations enabled simultaneously?
What was Rocket Contrib?
Why might a team maintaining an older Rocket codebase still encounter references to `rocket_contrib` in their `Cargo.toml` even if newer Rocket projects no longer need it for the same functionality?
Why is it useful context to know that some of Rocket Contrib's originally-separate features were later integrated more directly into Rocket's core framework over time?
What did Rocket Contrib's JSON support (before it was later integrated more directly into Rocket's core in later versions) typically provide for a Rocket application?
Why might a Rocket project explicitly declare a dependency on rocket_contrib's specific sub-features (like enabling only the "json" feature flag) rather than pulling in the entire contrib crate's functionality?