Is no-nill too strict?

Hi all! Thanks for this awesome eslint plugin! I can’t use null in objects, is that a bug or an expected behaviour? How can I solve this?

const defaultState = {
    token: null
}
export function reducer(state = defaultState, action){
    return state
}

/home/user/Scrivania/mercury-new/src/modules/auth/index.js
  3:12  error  Unallowed use of `null` or `undefined`  fp/no-nil

[jfmengels]

Yes, Maybe is a monad. I recommend reading this (relatively short) book https://github.com/MostlyAdequate/mostly-adequate-guide, which talks about them in this chapter and which I thought was pretty good last time I read it. This one is pretty nice too, but the section about monads and Maybe is not yet written. I’ll try to find a nice short article dealing with Maybe.

[avalanche1]

I use map() extensively with curly braces - which requires a return statement. Can we add a sub-rule for fp/no-nil to exclude map() from linting?