[ ] e.g.commitlint: what if commitlint object in package.json already exists, but with different content?
[ ] what if husky hook, intended for use for this current schematics, also exists, with different content? should we replace it? prepend it, as with pre-push?
[ ] check all schematics against the edge cases checklist
[ ] what if packages that schematics brings already are used in consuming repository, but their configs are not in package.json, but rather in .rc files? e.g. husky. - in that case we might specifically for each schematics (husky, and each and every other one) check if in consuming repo (tree) any of the available package configs exists, and then inform user about it, and maybe prompt him for an action (rewrite? create a backup of package.json (should we do it by default?)), etc.
[ ] what do we do if scripts we intend to add are already existing? in which cases do we prepend? in which do smth else?
[ ] e.g.commitlint: what if
commitlintobject in package.json already exists, but with different content?[ ] what if husky hook, intended for use for this current schematics, also exists, with different content? should we replace it? prepend it, as with
pre-push?[ ] check all schematics against the edge cases checklist
[ ] what if packages that schematics brings already are used in consuming repository, but their configs are not in package.json, but rather in .rc files? e.g. husky. - in that case we might specifically for each schematics (husky, and each and every other one) check if in consuming repo (tree) any of the available package configs exists, and then inform user about it, and maybe prompt him for an action (rewrite? create a backup of package.json (should we do it by default?)), etc.
[ ] what do we do if scripts we intend to add are already existing? in which cases do we prepend? in which do smth else?