refactor: split files

[jly36963]

Description

• Split functions into separate files
• Group files by kind
• Imports include file extensions
  • ESM import docs

[p9f]

I would really like to try to keep the tests close to the source (locality of behaviour mindset), do you think we could consider ways to achieve it?

One idea would be to group the utilities by types and then in each folder have all the source + tests:

native-utilities/
  join.ts
  join.test.ts
  ...
word-utilities/
  camelCase.ts
  camelCase.test.ts
  ...
object-utilities/
  camelKeys.ts
  camelKeys.test.ts
  deepCamelCase.ts
  ...

That might help to make the new naming convention clearer.
we could also merge the .type.test.ts and .test.ts files - as they will be quite small because of the split (see this)

[gustavoguichard]

I agree with the comments from @p9f .
Also.. I kind of hate camel cased filenames. I'd rather keep them in kebab case bc it works best in file system world - I've has troubles with that more than once. Do you have a strong reason to use them camel cased?

[jly36963]

I couldn't think of.a better name for the additional folder

[gustavoguichard]

I couldn't think of.a better name for the additional folder

I think the words method belongs to that folder even though it is used in the casing folder... maybe utils (which is also quite broad) sounds better?

[p9f]

maybe we remove the casing folder and:

• move toLowerCase and toUpperCase to the native folder
• having words-utils or just words for all the utils functions based on the words method? so that it's clear what the difference is between toLowerCase (not word based) and the other case methods (word based)?

[gustavoguichard]

move toLowerCase and toUpperCase to the native folder
Agreed

For the words method, I believe it should belong to the same folder as truncate and reverse from #71 which are not casing functions nor native ones but popular string utilities from other libs.

[jly36963]

For sure, will make those changes during lunch today. If you can think of any other feedback, let me know.
I'm hoping to get this merged quickly so as to avoid a lot of merge conflicts

[gustavoguichard]

@jly36963 to avoid conflicts I'll stop my activity until this PR is merged =)

[gustavoguichard]

LGTM