Fix ignoring schema when wildcard-key is defined

[florius0]

Currently, schemas with wildcard-key defined misbehave:

iex(1)> NimbleOptions.validate [], [table: [doc: "ETS table to use", type: :atom, default: nil], *: [type: :any]]
{:ok, []}
iex(2)> NimbleOptions.validate [], [table: [doc: "ETS table to use", type: :atom, default: nil]]
{:ok, [table: nil]}

The reason is that NimbleOptions.expand_star_to_option_keys/2 ignores all other keys, except present in the data when handling wildcard.

Is that intended?

[josevalim]

Yeah, I feel it should be [table: nil] for both, right @whatyouhide?

[coveralls]

Pull Request Test Coverage Report for Build e7ed4c95ea219a988286bc04378fe70620abab1a-PR-142

Details

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 93.793%

---

Totals
Change from base Build 19f7b2409832fade7541c576cfae03bd57b8a871:	0.0%
Covered Lines:	272
Relevant Lines:	290

---

💛 - Coveralls

[whatyouhide]

Yes I think this is a great change, I'd consider it a bug fix 🙃 Thank you @florius0 💟