> Null doesn't make any sense there, so I'd consider it invalid Perfect, see attached patch on OAK-635. I used a combo of @Nonnull and checkNotNull to enforce this constraint.
alex On Tue, Feb 19, 2013 at 10:22 AM, Michael Dürig <[email protected]> wrote: > +1 > Michael > On Feb 19, 2013 9:20 AM, "Jukka Zitting" <[email protected]> wrote: > > > Hi, > > > > On Tue, Feb 19, 2013 at 11:14 AM, Alex Parvulescu > > <[email protected]> wrote: > > > I'm looking at the Tree and the NodeState interfaces, I see a lot of > api > > > docs about the returned value but no constraints about the input child > > name. > > > Is null considered a valid input? > > > > Null doesn't make any sense there, so I'd consider it invalid. Empty > > strings should probably be treated equally. > > > > BR, > > > > Jukka Zitting > > >
