Rename entry for FormData.append's filename parameter#10695
Conversation
api/FormData.json
Outdated
| } | ||
| }, | ||
| "AppendWithFilename": { | ||
| "filename_argument": { |
There was a problem hiding this comment.
Nice! This is the kind of thing that I was trying to tackle with this new guideline: https://github.com/mdn/browser-compat-data/blob/main/docs/data-guidelines.md#parameters-and-parameter-object-features. Want to change this to use "parameter" instead of "argument"?
There was a problem hiding this comment.
Since you ask I have to say I don't quite want to use "parameter", since the "argument" terminology is baked into the platform itself, but consistency always wins and I see there are more foo_parameter than foo_argument entries in BCD. So I'll fall in line :)
There was a problem hiding this comment.
And pushing the rest of the data into line as well: #10700
There was a problem hiding this comment.
Yeah, "want" was probably the wrong word (I also thought it should've been argument, #10509, but MDN uses parameter far more often). Thank you!
This is more consistent with many foo_parameter entries, such as api.Element.requestFullscreen.options_parameter. Importantly, including an underscore makes it clear that it's not an exposed name of an API.
* Bump version to v3.3.6 * Add release note for #10646 * Add release note for #10581 * Add release note for #10685 * Add release note for #10691 * Add release note for #6957 * Add release note for #10721 * Add release note for #10695 * Add release note for #9821 * Add release note for #10681 * Add release note for #10725 * Add stats * Add release date * Wordsmith
This is more consistent with many foo_parameter entries, such as
api.Element.requestFullscreen.options_parameter.
Importantly, including an underscore makes it clear that it's not an
exposed name of an API.