@dblock or @mbleigh can you give me your thoughts on this. I am trying to think of an easy way to check the value of an attribute and hide it if it is nil.

I am really undecided at this point if this should be an option at the entity level or at the individual exposure level.

Either way, I think conditions_met should accept the attribute. Eventually I think we should pass it to the proc with the object but I think this is a breaking change because existing procs won't be able to handle it.

I think this is a pretty cool feature, and I definitely think it should be on a per-exposure basis. If you have a host of nullable exposures, you can use the new #with_options method that @mbleigh added recently to share that configuration easily while keeping the entity definition DRY. +1

I like the feature, and also agree that it should be per-exposure. There are some attributes that you may want to expose as null even if others aren't. Make it per-exposure and I'd say it's good to merge!

Note I'm not 100% if the current implementation is per-exposure, but it seems like the specs at least could use a bit more descriptive of names.

I agree. The naming is bad. This was intended to talk about, I wasn't planning to merge until I cleanup the specs and make sure i've covered what I need to.

The current implementation should be per-exposure.

Bump. What do we want to do about this one? If anything it needs a line in CHANGELOG :)

I need to fix it. I am just getting back into this now after some craziness.

In the spirit of staying positive, I think this should be renamed to expose_nil, which would default to true.

Note that exclude_nil can be implemented today with an if.

Okay, I should have time towards the end of the week to fix this. I am going to fix the implementation and I like the expose_nil wording.

So was this finally implemented?
I cant see anything about this on the Docs.

Thanks.

This hasn't been merged, see discussion above. Need more work (from @idyll or others).

Thanks @dblock
In the meanwhile just found this workaround that needs to be applied to every field.

http://stackoverflow.com/questions/21950613/grape-entities-conditional-expose-if-field-is-not-nil

Hope it help.
Cheers

I am closing this and will reopen a new one with my changes,

Was this ever re-opened in another issue? Would be a nice feature for with_options with infrequent relations.

with_options(expose_nil: false) do
  expose :snow_route
  expose :temporary_route
  expose :construction_warning
end