@dbx-tools/shared-core 0.3.1 → 0.3.3

package/package.json

@@ -22,7 +22,7 @@
   "publishConfig": {
     "access": "public"
   },
-  "version": "0.3.1",
+  "version": "0.3.3",
   "types": "index.ts",
   "type": "module",
   "exports": {

package/src/string.ts

@@ -33,7 +33,11 @@ type ResolvedIdentifierOptions = Required<
   IdentifierOptions & Pick<TokenizeOptions, "lowerCase" | "capitalize">
 >;
 
-const TOKENIZE_CAMEL_CASE_REGEXP = /[A-Z]?[a-z]+|[0-9]+|[A-Z]+(?![a-z])/g;
+// A leading `v`/`V` immediately followed by digits (a version marker like
+// `v2`) is kept as ONE token instead of splitting into `v` + `2`; it leads the
+// alternation so it wins over the generic letter / digit runs. Everything else
+// is the usual camelCase word / number / all-caps-acronym split.
+const TOKENIZE_CAMEL_CASE_REGEXP = /[vV][0-9]+|[A-Z]?[a-z]+|[0-9]+|[A-Z]+(?![a-z])/g;
 const TOKENIZE_NON_ALPHANUMERIC_REGEXP = /[a-zA-Z0-9]+/g;
 const TOKENIZE_OVERRIDES: ((token: string, options: TokenizeOptions) => string)[] = [
   (token, options) => {
@@ -42,6 +46,14 @@ const TOKENIZE_OVERRIDES: ((token: string, options: TokenizeOptions) => string)[
     }
     return token;
   },
+  // Version marker `v2` -> `V2` when capitalizing (the leading `v` uppercases,
+  // the digits stay), so it reads as one unit rather than "V 2".
+  (token, options) => {
+    if (options.capitalize && /^v[0-9]+$/.test(token)) {
+      return `V${token.slice(1)}`;
+    }
+    return token;
+  },
 ];
 const URI_REGEXP = /^([a-zA-Z][a-zA-Z0-9+.-]*)?:\/\/([^\s/?#][^\s]*)?$/;
 const EMAIL_REGEXP = /^([a-zA-Z0-9.!#$%&'*+/=?^_`{|}~-]+)@([a-zA-Z0-9-]+(?:\.[a-zA-Z0-9-]+)+)$/;