fix(types): make VNodeDirective properties optional, fix #8013

[KaelWD]

What kind of change does this PR introduce? (check at least one)

• Bugfix - fixes Unable to use directives in a render function with typescript #8013
• Feature
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
• All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
• New/updated tests are included

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
Prevents Property 'oldValue' is missing in type '{ name: string; value: string; }'. when using directives in a render function (see test).

There should probably actually be three different VNodeDirectives:

• In h('', data) - mostly optional, not readonly
• In VNodeData (returned from createElement) - normalised, not readonly
• In DirectiveFunction - the current definition (before this change)

[HerringtonDarkholme]

Thanks for your contribution!

Since VNodeDirective has optional properties, we cannot guarantee DirectiveFunction has non-nullable DirectiveBinding as argument. So I think changing VNodeDirective alone is OK.

[KaelWD]

You're right, console.log(h('div', { directives: [{ name: 'something' }] })) only has name. Inspecting the vnode after it's mounted shows def, modifiers, name.

Vue.directive('something', (el, binding) => { console.log(binding) }) also only has those three defined.

I'm thinking there should still be a separate definition for in vs out though, modifiers is always defined as an empty object but it doesn't make sense to pass that in through h.

Edit: yeah, forgot to check this after the change:

[KaelWD]

Bump @HerringtonDarkholme

edit: ty