Converts settings to TypeScript

[Zyie]

Description of change

Opening another draft PR to let people know what is being worked on.

So far I have tried to use namespaces for settings however this resulted in many setting objects instead of one large one, not sure why.

For now I have gone with one interface that has optional parameters for the options defined outside the initial settings file.

Let me know if you guys have a better solution to try out. I dont think the current method is bad just not great.

Pre-Merge Checklist

• Lint process passed (npm run lint)
• Tests passed (npm run test)

[codecov-io]

Codecov Report

Merging #6315 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #6315   +/-   ##
=======================================
  Coverage   77.24%   77.24%           
=======================================
  Files         178      178           
  Lines        9511     9511           
=======================================
  Hits         7347     7347           
  Misses       2164     2164

Impacted Files	Coverage Δ
packages/prepare/src/BasePrepare.js	73.43% <ø> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 955f964...c133585. Read the comment docs.

[bigtimebuddy]

I think this is fine. I'm not in love with the name PixiSettings, maybe simply Settings? We have bigger fish than settings. Lets get this in and we can try other approaches later.

[Zyie]

I'm not in love with the name PixiSettings, maybe simply Settings

I've updated the name

[ivanpopelyshev]

@bigtimebuddy @Zyie What about IPixiSettings and IRenderOptions ? Also , RenderOptions in core will have more settings than that, and they will be optional. What about IBaseRenderOptions ?'

For example, it doesnt have resolution.

[ivanpopelyshev]

I approve it anyway, because I can change RenderOptions in @pixi/core PR.

[Zyie]

What about IPixiSettings and IRenderOptions ?'

Would it be a good idea to have a naming convention for interfaces. So all begin with I? That way we dont have a mashup of different names. For example we have IPoint, IDestoryOptions, but DecomposedDataUri, Settings, RenderOptions

For example, it doesnt have resolution.

Ah yes i didnt realise that got added dynamically in AbstractRenderer.

[ivanpopelyshev]

I think DecomposedDataUri is the only one without I

[bigtimebuddy]

I like using I as a prefix for interfaces.

[Zyie]

Ok I've updated the names to use the prefix. I'll let @ivanpopelyshev fix whatever needs to be fixed in his core pr