5

The tag has been included in https://meta.stackexchange.com/questions/128315/the-great-stack-overflow-tag-question-cleanup-of-2012, with the comment

(not sure about this one, it seems strange and has a smell, please provide input)

Input was provided. Of course, since this was the 68th answer, it didn't receive much attention.

The tag wiki has no reservation anyway.

DO NOT USE - Removed as part of "The great Stack Overflow tag/question cleanup of 2012" - See link in Tag Wiki for more information.

A simple google search shows that this is a well-known programming concept, at least in the Ruby on Rails community; a perfectly cromulent tag. Please remove this tag from the cleanup list.

(I tried proposing a tag wiki. I'm not a RoR programmer nor more generally a web programmer, so if you're familiar with the concept, please improve.)

|improve this question
  • Can it at least be renamed to something less generic, like "rails-mass-assignment"? – Nicol Bolas Jun 3 '12 at 21:12
  • @NicolBolas The phrase “mass assignment” is predominantly used by the RoR community, but it's also used outside, and the concept is generic (e.g. 1 in ASP.NET MVC, 2 in PHP). So the tag name should remain framework-agnostic. – Gilles 'SO- stop being evil' Jun 3 '12 at 21:17
  • The problem is that, because the phrase is so generic, anyone who doesn't know what it's really referring to can use it incorrectly. – Nicol Bolas Jun 3 '12 at 21:24
  • @NicolBolas Anyone can use a tag incorrectly, but I don't see any evidence of misuse of this tag. Has there been a posse on it recently? If (almost) no one is using the tag incorrectly (even though there was no tag wiki!), what's wrong with the tag? – Gilles 'SO- stop being evil' Jun 3 '12 at 21:35
2

mass assignment is the term used to describe:

  • The assigning of all attributes at once;
  • Multiple variables getting assigned to the respective values on a single line.

Nowadays, the mass assignment feature is commonly known as mass assignment vulnerabilities, due to the harm that it brings to applications.

Take the example of: GitHub user exploited a security vulnerability in the public key update

So, this term mass assignment, well known among RoR and ASP.NET programmers, proves to be useful in the current tag form, since it is a specific functionality and can also refer to the very problematic situations that comes with it.

And so, I express my agreement to keep the tag as it is.

|improve this answer

Not the answer you're looking for? Browse other questions tagged .