summaryrefslogtreecommitdiff
path: root/README.md
Commit message (Collapse)AuthorAgeFilesLines
...
* Allow Mash subclasses to disable warningsMichael Herold2017-02-041-0/+14
| | | | | | | | | | | | | | | | | Since we are transitively used as a dependency in many projects, we should have given the ability to toggle this behavior off. The logging feature is more of a "help people get started with Mash" feature. If you're using Hashie in a library, it's likely that you already know the tradeoffs of attempting to override methods on the object. To use this feature, you only have to subclass Mash and then call the class method: ```ruby class KeyStore < Hashie::Mash disable_warnings end ```
* Prepare for next development iteration, 3.5.2Michael Herold2017-01-311-1/+1
|
* Prepare for release of 3.5.1v3.5.1Michael Herold2017-01-311-1/+1
|
* Add MergeInitializer to Coercian examplePaul Bowsher2016-12-011-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | Before: ```ruby class Tweet < Hash include Hashie::Extensions::Coercion coerce_key :user, User end user_hash = { name: "Bob" } Tweet.new(user: user_hash) # => {} ``` After: ```ruby class Tweet < Hash include Hashie::Extensions::Coercion include Hashie::Extensions::MergeInitializer coerce_key :user, User end user_hash = { name: "Bob" } Tweet.new(user: user_hash) #=> {:user=>#<struct User name={:name=>"Bob"}>} ```
* Add a logging layer to address common issues (#381)Michael Herold2016-11-021-0/+9
|
* Preparing for next development iteration, 3.4.7.dblock2016-09-161-1/+1
|
* Preparing for release, 3.4.6.v3.4.6dblock2016-09-161-1/+1
|
* Preparing for next development iteration, 3.4.6.dblock2016-09-161-1/+1
|
* Preparing for release, 3.4.5.v3.4.5dblock2016-09-161-1/+1
|
* Hashie::Mash.load accepts a Pathname object. Closes #331.Atsushi Ishida2016-07-151-0/+7
| | | | https://github.com/intridea/hashie/issues/331
* Preparing for the next development iteration, 3.4.5.dblock2016-04-291-1/+1
|
* Preparing for release, 3.4.4.v3.4.4dblock2016-04-291-1/+1
|
* Omit `return'camelmasa2016-02-231-3/+3
|
* Fix too fexible regexcamelmasa2016-02-231-1/+1
|
* README: fix typoPrayag Verma2016-02-061-1/+1
| | | | Found a spelling mistake - includeable → includable
* README: Clarified IndifferentAccess docsChristian Höltje2016-01-261-2/+23
| | | | | | Tried to make the IndifferentAccess documentation clearer. Closes #340
* Update README.mdVasiliy Yorkin2015-12-171-1/+1
|
* Preparing for next development iteration, 3.4.4. [ci skip]dblock2015-10-251-2/+2
|
* Preparing for release, 3.4.3. [ci skip]v3.4.3dblock2015-10-251-4/+4
|
* SRP: The StrictKeyAccess extension will raise an error whenever a key is ↵Peter Boling2015-10-231-0/+19
| | | | | | | | | | | | | | | | | | | | | | accessed that does not exist in the hash. In Python a "Hash" is called a "Dictionary", and ... > "It is an error to extract a value using a non-existent key." See: https://docs.python.org/2/tutorial/datastructures.html#dictionaries EXAMPLE: class StrictHash < Hash include Hashie::Extensions::StrictKeyAccess end >> hash = StrictHash[foo: "bar"] => {:foo=>"bar"} >> hash[:foo] => "bar" >> hash[:cow] KeyError: key not found: :cow
* Introduce Hashie::Extensions::Dash::Coercion.Vladimir Kochnev2015-08-311-0/+30
|
* Preparing for next release, 3.4.3Michael Herold2015-06-021-1/+1
|
* Preparing for release 3.4.2v3.4.2Michael Herold2015-06-021-1/+1
|
* The hashie_rails gem is now hashie-forbidden_attributes.Daniel Doubrovkine (dB.) @dblockdotorg2015-05-191-1/+1
|
* Merge pull request #297 from michaelherold/property-translationDaniel Doubrovkine (dB.) @dblockdotorg2015-04-301-1/+46
|\ | | | | Extract Trash behavior into an extension
| * Update readme with PropertyTranslation docsMichael Herold2015-04-291-1/+46
| |
* | Add documentation about circular coercioncircular-coercion-docsMichael Herold2015-04-261-0/+35
|/ | | | | | | | | | | | | | | | | | | | | | | The `coerce_key` method in the Coercion extension is a class-level method. As such, using circular coercion is not possible without using a coercion proc/lambda, since the coercion in the first type will not have the second type defined at load time. This can be worked around through the use of a coercion proc. I have added docs about this to the README, as well as tests that demonstrate the behavior. I don't see this as a bug, since doing this raises a Ruby-level error that makes sense. The only way I can think of to make the non-working demonstration work that I can think of would make the DSL a lot noisier (i.e. make all of the "intos" use procs/lambdas to yield the class name/structure that you'd like. Something like `coerce_key :model, to: -> { Model }`, which then grabs that returned `Model` and is applied. I think this is a reduction in user experience, so I chose not to pursue it. Fixes #115
* Minor fix in docKonstantin Delchev2015-04-031-1/+1
|
* Added Gitter badgeThe Gitter Badger2015-02-231-0/+2
|
* Added Hashie::Extensions::DeepLocateMichael Sievers2015-02-031-0/+42
|
* Update README.mdGoT2015-01-151-1/+1
| | | Just fix example in README.
* Updated badges to look nice.Daniel Doubrovkine (dB.) @dblockdotorg2014-12-301-1/+7
|
* Corrected typo.dblock2014-12-301-9/+5
|
* Public utility methods for stringify/symbolize keysMax Lincoln2014-12-301-0/+13
|
* Add block to Extensions::DeepMergeIlya Kamenko2014-12-301-0/+15
|
* Support for conditionally required Dash propertiesChris Cashwell2014-12-111-0/+8
|
* SafeAssignment will now also protect hash-style assignments.Jonathan Rochkind2014-12-091-1/+2
|
* Code coverage reportingBartosz Kopiński2014-11-271-1/+1
|
* fixed documentationTaylor Martin2014-10-221-1/+1
|
* Merge pull request #234 from cvengros/patch-1Daniel Doubrovkine (dB.) @dblockdotorg2014-10-101-5/+2
|\ | | | | README.md: Fixed issue in deep_merge example
| * README.md: Fixed issue in deep_merge example Petr Cvengros2014-10-091-5/+2
| | | | | | The way it was written doesn't work, because h1 and h2 will be standard Hashes (not MyHashes) that don't have the deep_merge method.
* | Custom error messages for required properties in Hashie::Dash subclassesPetr Balaban2014-10-071-4/+8
|/
* Preparing for 3.3.1 release.dblock2014-08-261-1/+1
|
* Preparing for next releaseMichael Herold2014-08-261-1/+1
|
* Preparing for release, 3.3.0v3.3.0Michael Herold2014-08-261-1/+1
|
* Add Hashie::Extensions::DeepFindMichael Herold2014-08-221-0/+26
| | | | | | | | | | | | This extension adds a `#deep_find` (aliased as `#deep_detect`) and a `#deep_find_all` (aliased as `#deep_select`) method to any Hash-like object. These methods perform a depth-first search on the object and its values and return either the first occurrence (for `#deep_find`) or an array of all occurrences (for `#deep_find_all`) within the nested structure of the hash. They work for nested Hash-like objects and nested Enumerables. [Closes #156]
* Add Hashie::Extensions::Mash::SafeAssignmentMichael Herold2014-08-201-0/+15
| | | | This is part 3 of 3 of the to-do list determined in #198.
* Add Hashie::Extensions::MethodOverridingWriterMichael Herold2014-08-201-0/+23
| | | | This is part 2 of 3 of the to-do list determined in #198.
* Merge pull request #203 from michaelherold/update-mash-readmeDaniel Doubrovkine (dB.) @dblockdotorg2014-08-201-1/+12
|\ | | | | Update the README for Mash
| * Update the README for MashMichael Herold2014-08-201-1/+12
| | | | | | | | This is part 1 of 3 of the to-do list determined in #198.
View Lorry Controller Status