lukaszlenart opened a new pull request, #316: URL: https://github.com/apache/struts-site/pull/316
Documents the JSON parameter-filtering work for Struts 7.3.0. Content audit of the following framework PRs: - apache/struts#1773 (WW-4858, **merged**) — JSON population now honors Parameters Interceptor-style name/value filtering. - apache/struts#1784 (WW-4858, **open**) — `@StrutsParameter` getter enforcement at `depth ≥ 1` for scalar collection elements. - apache/struts#1775 (WW-5643) and apache/struts#1776 (WW-5644) — internal reader/writer thread-safety fixes, **no doc surface** (no config change), so not documented here. ## Changes **`source/plugins/json/index.md`** — new *Input parameter filtering* subsection: - Always-on: framework-wide accepted/excluded name patterns, `paramNameMaxLength` (default `100`), `ParameterNameAware`/`ParameterValueAware`, `@StrutsParameter`. - Opt-in: `acceptedValuePatterns`, `excludedValuePatterns`, `applyPropertyFiltersToInput`. **`source/core-developers/struts-parameter-annotation.md`** — migration callout: JSON/REST scalar-collection element paths (`mySelection[0]`) are now authorized on the **getter at `depth = 1`** (previously the container setter, `depth = 0`). All config names/defaults verified against merged `main` (not the PR descriptions). ## Notes - `#1784` is still open; its documented behavior is not yet in a released tag. If its scope changes before merge, the parameter-annotation page may need a follow-up. - Local `jekyll build` could not run (broken system Ruby bundler); relying on the staging auto-build. Internal link targets verified to exist. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
