Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 12-9-stable
  • 12-7-stable
  • 12-6-stable
  • 12-8-stable
  • github/fork/Kloppi313/patch-1
  • 12-5-stable
  • 12-4-stable
  • github/fork/ramalokesh8477/master
  • 12-1-stable
  • 12-2-stable
  • 12-0-stable
  • 12-3-stable
  • 42-42-stable
  • github/fork/hussamgit398/patch-2
  • 12-3-auto-deploy-20190911
  • 12-3-auto-deploy-20190916
  • 12-3-auto-deploy-20190908
  • 12-3-auto-deploy-20190901
  • 12-3-auto-deploy-20190901-32664
  • v12.10.0.pre
  • v12.9.0
  • v12.9.0-rc42
  • v12.8.7
  • v12.8.6
  • v12.8.5
  • v12.8.4
  • v12.8.3
  • v12.6.8
  • v12.7.7
  • v12.8.2
  • v12.8.1
  • v12.9.0.pre
  • v12.8.0
  • v12.8.0-rc42
  • v12.5.10
  • v12.7.6
  • v12.6.7
  • v12.7.5
  • v12.5.9
40 results

commit_status.rb

  • Jan Provaznik's avatar
    0665a8f7
    Enable mapping to nil in enums · 0665a8f7
    Jan Provaznik authored
    Enum in Rails 5 does not map nil values - IOW nil value remains nil,
    even if there is a key with nil value in the enum definition.
    
    This commit overrides the underlying Enum methods so nil value is
    still mapped. This solution is far from being ideal: it uses dynamic
    definition of methods which introduces more magic/confusion
    into the codebase.
    
    It would be better to get rid of the nil value in enums.
    0665a8f7
    History
    Enable mapping to nil in enums
    Jan Provaznik authored
    Enum in Rails 5 does not map nil values - IOW nil value remains nil,
    even if there is a key with nil value in the enum definition.
    
    This commit overrides the underlying Enum methods so nil value is
    still mapped. This solution is far from being ideal: it uses dynamic
    definition of methods which introduces more magic/confusion
    into the codebase.
    
    It would be better to get rid of the nil value in enums.