fixed camel case?

[DerekL27]

Why

Ticket
Ticket

This PR

Fixes camel case? Not sure if this is what the ticket meant

[coveralls]

Pull Request Test Coverage Report for Build 1091798901

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 17.037%

---

Totals
Change from base Build 1049750552:	0.0%
Covered Lines:	250
Relevant Lines:	1250

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 1164376598

• 1 of 23 (4.35%) changed or added relevant lines in 3 files are covered.
• 21 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.07%) to 16.947%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/utils/helpers.tsx	1	3	33.33%
src/components/userDirectory/CreateUser.tsx	0	3	0.0%
src/containers/userDirectory/index.tsx	0	17	0.0%

Files with Coverage Reduction	New Missed Lines	%
src/containers/pastSubmissionsReports/PastSubmissionReports.tsx	7	0%
src/containers/userDirectory/index.tsx	14	0%

Totals
Change from base Build 1116631719:	-0.07%
Covered Lines:	251
Relevant Lines:	1260

---

💛 - Coveralls

[justinkonecny]

Screenshots?

Did you test this to make sure it doesn't break anything?

[granttebeau]

Still have camel case here for the country and privilege columns, we'll need to make these normal case as well in the user directory

[DerekL27]

@justinkonecny
@granttebeau

should be fixed now

[granttebeau]

LGTM

[maxsebso]

The problem we had last time was that the form item would now contain no camel case. This would mean the request would come back bad request because the backend would be expecting camel case. If you are sure that you tested this thoroughly I will approve. If it is not tested it can and will break the whole form.

[DerekL27]

The problem we had last time was that the form item would now contain no camel case. This would mean the request would come back bad request because the backend would be expecting camel case. If you are sure that you tested this thoroughly I will approve. If it is not tested it can and will break the whole form.

Yeah you're right it did break the form. I changed it so that it takes the enum and formats it to look nice so now everything should be good. I tested it and it works

[maxsebso]

Almost! Just one thing. Since you are using the function convertEnumToRegularText 3 times in 3 different files you should put it in utils folder and then import it when it needs to be used

[DerekL27]

Almost! Just one thing. Since you are using the function convertEnumToRegularText 3 times in 3 different files you should put it in utils folder and then import it when it needs to be used

Smart

[rymaju]

Small nitpick ⛏️ otherwise LGTM

[rymaju]

Suggested change

	export const convertEnumToRegularText = (input: string) => {
	export const convertEnumToRegularText = (input: string): string => {

[maxsebso]

LGTM