The way #destructive_fields is written, you can't create fields on your documents with names like 'p' and 'y' because those conflict with Kernel#p and Kernel#y (from YAML), respectively. Could we tone down the strictness on this a bit so I can have my y field work again? Perhaps destructive_fields can exclude private Object methods?
- Assignee:
- Unassigned
- Reporter:
- Max Aller
- Votes:
-
0 Vote for this issue
- Watchers:
-
0 Start watching this issue
- Created:
- Updated:
- Resolved: