Not sticking to naming convention

[tabacitu]

I have just one big problem with this package - its name. All other Backpack packages use StudlyCase (aka PascalCase), but this ONE package uses kebab-case. Before we launch it, we could maybe rename it to ReviseOperation, because:

• it would fix the inconsistency
• it looks more professional anyway (arguably)

But. There's a reason I chose kebab-base when creating this package:

• the namespace looks MUCH better as kebab-case; it's a lot easier to read code that says revise-operation::view than reviseoperation::view;
• this operation will set an example for add-ons that people create; do we want them to use kebab-case or PascalCase?
• even for the package name, in Github and Composer, it's a lot easier to read and use a package if it's kebab-case; examples:

  > composer require vendor-name/backpack-moderate-operation
  > composer require vendor-name/backpack-soft-delete-buttons
  > composer require vendor-name/backpack-json-field
  # vs
  > composer require vendorname/backpackmoderateoperation 
  > composer require vendorname/backpacksoftdeletebuttons 
  > composer require vendorname/backpackjsonfield 

So I think for add-ons (operations, fields, etc), kebab-case is a better choice. But we've already chosen PascalCase for previous projects. Soo... we either have to:

• use PascalCase to have them all the same
• use kebab-case and live with the inconsistency

😞

[tabacitu]

Hmm... Laravel, ThePHPLeague, Symfony - they all use kebab-case for their Github projects. So let's just conquer our OCD and use kebab-case from now on. And recommend others do the same...