fix: use correct typings for config:init command

[connorjburton]

Summary

The config:init command would generate the config with the incorrect typings. This documentation page shows what the typings should be.

Test plan

I did not see any tests for the config command. There probably should be some but I am not sure this PR is the appropriate place to write tests for the config command(s).

This particular change could be tested, but writing a test to make sure the string is what I changed it to is not really a test, I am not familiar enough with ts-jest to suggest a better approach to test this.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[mrazauskas]

Nice and quick!

Isn’t it that the script still creates outdated config with globals instead of transform key? Or am I misreading?

[ahnpnl]

You are right that it is still generating the deprecated config. Candidate for another PR:)

[connorjburton]

Turns out there are tests, I did not look hard enough.

Going to address the tests and the other deprecated config

[ahnpnl]

Turns out there are tests, I did not look hard enough.

Going to address the tests and the other deprecated config

I already pushed:)

[connorjburton]

Thank you @ahnpnl! Do you want me to create a different PR for updating the deprecated config?

[coveralls]

Pull Request Test Coverage Report for Build 3107636585

• 0 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.3%) to 96.353%

---

Totals
Change from base Build 3089488315:	0.3%
Covered Lines:	3993
Relevant Lines:	4090

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 3107636585

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.3%) to 96.353%

---

Totals
Change from base Build 3089488315:	0.3%
Covered Lines:	3993
Relevant Lines:	4090

---

💛 - Coveralls

[ahnpnl]

Thank you @ahnpnl! Do you want me to create a different PR for updating the deprecated config?

Yes feel free to do so:)