feat(kit): support capture in input files

[splincode]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows Conventional Commits
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Refactoring
• Code style update
• Build or CI related changes
• Documentation content changes

What is the current behavior?

Closes #3063

IMG_6824.MOV

What is the new behavior?

IMG_6825.MOV

Does this PR introduce a breaking change?

• Yes
• No

[lumberjack-bot]

Pull request was closed ✔️

All saved screenshots (for current PR) were deleted 🗑️

[bundlemon]

BundleMon

Files updated (2)

Status	Path	Size	Limits
✅	demo/browser/main.(hash).js	325.06KB (+649B +0.2%)	+10%
✅	demo/browser/runtime.(hash).js	34.24KB (+38B +0.11%)	+10%

Unchanged files (3)

Status	Path	Size	Limits
✅	demo/browser/vendor.(hash).js	205.35KB	+10%
✅	demo/browser/polyfills.(hash).js	19.92KB	+10%
✅	demo/browser/scripts.(hash).js	14.92KB	+10%

Total files change +687B +0.11%

Groups updated (1)

Status	Path	Size	Limits
✅	demo/browser/*..js	2.19MB (+1.77KB +0.08%)	-

Final result: ✅

View report in BundleMon website ➡️

---

Current branch size history | Target branch size history

[github-actions]

Visit the preview URL for this PR (updated for commit 9a4c834):

https://taiga-ui--pr3065-splincode-feat-issue-dxxeogyt.web.app

_{(expires Sat, 26 Nov 2022 08:29:08 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 4b5ece1e114386f6a105425ef799091475b249eb}

[codecov]

Codecov Report

Base: 61.81% // Head: 66.96% // Increases project coverage by +5.14% 🎉

Coverage data is based on head (9a4c834) compared to base (4ba47cd).
Patch coverage: 31.25% of modified lines in pull request are covered.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3065      +/-   ##
==========================================
+ Coverage   61.81%   66.96%   +5.14%     
==========================================
  Files        1495      773     -722     
  Lines       17659     9740    -7919     
  Branches     2416     1377    -1039     
==========================================
- Hits        10916     6522    -4394     
+ Misses       6298     2987    -3311     
+ Partials      445      231     -214     

Flag	Coverage Δ
addon-charts	86.77% <ø> (+14.28%)	⬆️
addon-doc	48.40% <ø> (ø)
addon-editor	51.23% <ø> (ø)
addon-mobile	62.31% <ø> (ø)
addon-table	63.91% <ø> (ø)
addon-tablebars	∅ <ø> (∅)
cdk	∅ <ø> (∅)
core	∅ <ø> (∅)
kit	73.94% <31.25%> (-0.22%)	⬇️
summary	66.96% <31.25%> (+5.14%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...it/components/input-files/input-files.component.ts	17.07% <8.69%> (-0.74%)	⬇️
...it/components/input-files/input-files.directive.ts	31.25% <31.25%> (ø)
.../kit/components/input-files/input-files.options.ts	83.33% <83.33%> (ø)
projects/kit/components/input-files/index.ts	100.00% <100.00%> (ø)
...s/kit/components/input-files/input-files.module.ts	100.00% <100.00%> (ø)
projects/core/tokens/mode.ts
projects/core/internal/index.ts
...ore/components/notification/notification.module.ts
projects/core/components/calendar/index.ts
projects/cdk/classes/validation-error.ts
... and 719 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[waterplea]

Interesting. We already have 3 attributes that we just pass through to the native file. I wonder if it makes sense to expose native tag instead,

[splincode]

@waterplea We already have 3 attributes that we just pass through to the native file. I wonder if it makes sense to expose native tag instead

we can implement as a feature in separate PR

[waterplea]

@waterplea We already have 3 attributes that we just pass through to the native file. I wonder if it makes sense to expose native tag instead

we can implement as a feature in separate PR

Sure. Will you file an issue?

[splincode]

@waterplea fixed

[well-done-bot]