npm eslint-plugin-boundaries 7.4.2
Invalid capture lists no longer stop ESLint

latest releases: 7.4.4, 7.4.3
16 days ago

eslint-plugin v7.4.2

Changed

  • chore: Upgrade @boundaries/elements to 3.3.2, @boundaries/config to 1.0.1 and @boundaries/policies to 1.0.1.

Fixed

  • fix(#622): Warn about an element or file descriptor whose capture or baseCapture is set and is not an array, such as capture: "name", and ignore it. ESLint stopped with an error such as descriptor.capture.join is not a function when it loaded any rule, except for the baseCapture of a file descriptor, which the plugin used taking each character as a name; write the names in an array to keep using that descriptor.
  • fix(#622): Each configuration block uses its own boundaries/files descriptors when the settings of several blocks differ only in the basePattern or baseCapture of a file descriptor. Since 7.0.0, the plugin used the descriptors of the first of those blocks it linted for all of them, so errors may appear or disappear in the others.

elements v3.3.2

Fixed

  • fix(#622): isElementDescriptor and isFileDescriptor return false for a descriptor whose capture or baseCapture is set and is not an array, and getMatcher throws the error of an invalid descriptor for it and for a null or undefined descriptor. It threw an error such as descriptor.capture.join is not a function instead, except for the baseCapture of a file descriptor, whose characters it took as names.
  • fix(#622): getMatcher no longer returns the matcher of another configuration that differs only in the basePattern or baseCapture of a file descriptor, or in patterns or capture names that it wrote as the same text in its cache key, such as pattern: "a,b" and pattern: ["a", "b"].

config v1.0.1

Changed

  • chore: Upgrade @boundaries/elements to 3.3.2.

Fixed

  • fix(#622): normalizeSettings and normalizeConfig report an element or file descriptor whose capture or baseCapture is set and is not an array as invalid, and leave it out.

policies v1.0.1

Changed

  • chore: Upgrade @boundaries/elements to 3.3.2 and @boundaries/config to 1.0.1.

Fixed

  • fix(#622): getMatcher and the functions that use it, such as describeEntity and describeDependency, use the file descriptors of the settings they receive when other settings differ from them only in the basePattern or baseCapture of a file descriptor. They used the descriptors of the first of those settings.

Don't miss a new eslint-plugin-boundaries release

NewReleases is sending notifications on new releases.