Information for RPM rh-nodejs4-nodejs-sorted-object-1.0.0-5.el6.noarch.rpm
| ID | 60215 | ||||||
|---|---|---|---|---|---|---|---|
| Name | rh-nodejs4-nodejs-sorted-object | ||||||
| Version | 1.0.0 | ||||||
| Release | 5.el6 | ||||||
| Epoch | |||||||
| Arch | noarch | ||||||
| Summary | Returns a copy of an object with its keys sorted | ||||||
| Description | Although objects in JavaScript are theoretically unsorted, in practice most engines use insertion order—at least, ignoring numeric keys. This manifests itself most prominently when dealing with an object's JSON serialization. So, for example, you might be trying to serialize some object to a JSON file. But every time you write it, it ends up being output in a different order, depending on how you created it in the first place! This makes for some ugly diffs. sorted-object gives you the answer. Just use this package to create a version of your object with its keys sorted before serializing, and you'll get a consistent order every time. | ||||||
| Build Time | 2016-07-19 08:08:04 GMT | ||||||
| Size | 5.32 KB | ||||||
| cff07a734af061426079f7dfc05ee4af | |||||||
| License | WTFPL | ||||||
| Buildroot | sclo6-rh-nodejs4-rh-el6-build-15348-21679 | ||||||
| Provides |
|
||||||
| Obsoletes | No Obsoletes | ||||||
| Conflicts | No Conflicts | ||||||
| Requires |
|
||||||
| Recommends | No Recommends | ||||||
| Suggests | No Suggests | ||||||
| Supplements | No Supplements | ||||||
| Enhances | No Enhances | ||||||
| Files | |||||||
| Component of | No Buildroots |
