Questions from maintainer about mockingcase HOT 4 CLOSED

Hi @strdr4605,

• Should the mOcKiNgCaSe be exported as default?

Yes. if that the only functionality you are exposing.

• Should the mOcKiNgCaSe function be renamed in mockingcase?

How about MockingCase instead.

• For consistency, should the Definition file, Main file and Test file have all index or mockingcase name?

It comes down to your personal preference. my personal preference and what I have observed from several project is as follow.

• type-definations are kept inside a types directory.
• keep functionality under offering-package.js and test under offering-package.test.js. import them to index.js and then expose that/those api(s).

from mockingcase.

@distalx thank you for feedback.

type-definations are kept inside a types directory.

As the package is not big I don't want to have redundant folders.

One solution could be to move the main files to src folder

...

• src
  • mockingcase.d.ts
  • mockingcase.js
  • mockingcase.test.js

...

How about MockingCase instead.

The name only affects how you call the function in the browser by CDN. MockingCase is a class name, so maybe better to stick with mockingCase or mockingcase as in first place it is a function ?!

from mockingcase.

In that case mockingCase or mockingcase both sounds good.

from mockingcase.

Closing as most of the questions resolved

from mockingcase.