mirror of
https://github.com/google/nomulus.git
synced 2025-04-30 12:07:51 +02:00
9d2b1e7572
Currently, we have two different ways to parse a "set" parameter: key=value1&key=value2&key=value3... and keys=value1,value2,value3 This is error prone for several reasons: - different parts of the code must be "synchronized" to use the same style (the place that creates the request, and the place that parses the request) - for the key=value1&key=value2, we often use the same key name for the single value and the set value. This can result in subtle bugs where part of the code will successfully read the key assuming there's only one key (and will get the first key=value1, ignoring the rest) Here we transition everything to the keys=value1,value2,value3 method. This one was chosen because: - it's shorter - it's more intuitive for users - the key name is plural, differentiating it from the singular key=value that other requests might need ----------------------------------- To make sure there are not "transition issues", we will continue to support (with warnings) the key=value1&key=value2 parameter parsing until we're sure we haven't forgotten to update any part of the code. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=198810681 |
||
|---|---|---|
| .. | ||
| BatchComponent.java | ||
| BatchModule.java | ||
| BUILD | ||
| DeleteContactsAndHostsAction.java | ||
| DeleteLoadTestDataAction.java | ||
| DeleteProberDataAction.java | ||
| EntityIntegrityAlertsSchema.java | ||
| ExpandRecurringBillingEventsAction.java | ||
| MapreduceEntityCleanupAction.java | ||
| MapreduceEntityCleanupUtil.java | ||
| RefreshDnsOnHostRenameAction.java | ||
| ResaveAllEppResourcesAction.java | ||
| VerifyEntityIntegrityAction.java | ||
| VerifyEntityIntegrityStreamer.java | ||