Fix: Allow non_camel_case_types on derived SystemParamBuilder generics

[Fachep]

Objective

Fix non_camel_case_types warning emitted by generic type parameters generated by #[system_param(builder)].

#[derive(SystemParam)]
#[system_param(builder)]
struct MySystemParam<'w, 's> {
    query_field: Query<'w, 's ,Entity>,
}

> cargo check
...
warning: type parameter `Bquery_field` should have an upper camel case name
   --> src\lib.rs:171:9
    |
171 |         query_field: Query<'w, 's ,Entity>,
    |         ^^^^^^^^^^^ help: convert the identifier to upper camel case: `BqueryField`
...

Solution

Add #[allow(non_camel_case_types)] to each generated type parameter when declaring, in the SystemParam derive macro.

Testing

By referencing this branch in Cargo.toml, the warning no longer occurs for the usage above when running cargo check.

[github-actions]

Welcome, new contributor!

Please make sure you've read our contributing guide and we look forward to reviewing your pull request shortly ✨

[Copilot]

Pull request overview

This PR fixes a compiler warning for generated type parameters in the SystemParam derive macro when using the #[system_param(builder)] attribute. The macro generates type parameters by prefixing field names with "B", which creates non-camel-case identifiers (e.g., Bquery_field) that trigger linting warnings.

• Added #[allow(non_camel_case_types)] attribute to generated type parameters to suppress the warning

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[alice-i-cecile]

A comment here might be nice, but this is a perfectly fine fix.