Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package rubygem-regexp_parser for
openSUSE:Factory checked in at 2022-05-16 18:08:34
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/rubygem-regexp_parser (Old)
and /work/SRC/openSUSE:Factory/.rubygem-regexp_parser.new.1538 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "rubygem-regexp_parser"
Mon May 16 18:08:34 2022 rev:9 rq:977458 version:2.4.0
Changes:
--------
---
/work/SRC/openSUSE:Factory/rubygem-regexp_parser/rubygem-regexp_parser.changes
2022-04-30 22:52:57.820258820 +0200
+++
/work/SRC/openSUSE:Factory/.rubygem-regexp_parser.new.1538/rubygem-regexp_parser.changes
2022-05-16 18:11:01.585397888 +0200
@@ -1,0 +2,45 @@
+Mon May 16 07:51:38 UTC 2022 - Manuel Schnitzer <mschnit...@suse.com>
+
+- updated to version 2.4.0
+
+ ### Fixed
+
+ - fixed interpretation of `+` and `?` after interval quantifiers (`{n,n}`)
+ - they used to be treated as reluctant or possessive mode indicators
+ - however, Ruby does not support these modes for interval quantifiers
+ - they are now treated as chained quantifiers instead, as Ruby does it
+ - c.f. [#3](https://github.com/ammar/regexp_parser/issues/3)
+ - fixed `Expression::Base#nesting_level` for some tree rewrite cases
+ - e.g. the alternatives in `/a|[b]/` had an inconsistent nesting_level
+ - fixed `Scanner` accepting invalid posix classes, e.g. `[[:foo:]]`
+ - they raise a `SyntaxError` when used in a Regexp, so could only be
passed as String
+ - they now raise a `Regexp::Scanner::ValidationError` in the `Scanner`
+
+ ### Added
+
+ - added `Expression::Base#==` for (deep) comparison of expressions
+ - added `Expression::Base#parts`
+ - returns the text elements and subexpressions of an expression
+ - e.g. `parse(/(a)/)[0].parts # => ["(", #<Literal @text="a"...>, ")"]`
+ - added `Expression::Base#te` (a.k.a. token end index)
+ - `Expression::Subexpression` always had `#te`, only terminal nodes lacked
it so far
+ - made some `Expression::Base` methods available on `Quantifier` instances,
too
+ - `#type`, `#type?`, `#is?`, `#one_of?`, `#options`, `#terminal?`
+ - `#base_length`, `#full_length`, `#starts_at`, `#te`, `#ts`, `#offset`
+ - `#conditional_level`, `#level`, `#nesting_level` , `#set_level`
+ - this allows a more unified handling with `Expression::Base` instances
+ - allowed `Quantifier#initialize` to take a token and options Hash like
other nodes
+ - added a deprecation warning for initializing Quantifiers with 4+ arguments:
+
+ Calling `Expression::Base#quantify` or `Quantifier.new` with 4+ arguments
+ is deprecated.
+
+ It will no longer be supported in regexp_parser v3.0.0.
+
+ Please pass a Regexp::Token instead, e.g. replace `type, text, min, max,
mode`
+ with `::Regexp::Token.new(:quantifier, type, text)`. min, max, and mode
+ will be derived automatically.
+
+ This is consistent with how Expression::Base instances are created.
+
+-------------------------------------------------------------------
Old:
----
regexp_parser-2.3.1.gem
New:
----
regexp_parser-2.4.0.gem
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ rubygem-regexp_parser.spec ++++++
--- /var/tmp/diff_new_pack.szk9tS/_old 2022-05-16 18:11:02.065398269 +0200
+++ /var/tmp/diff_new_pack.szk9tS/_new 2022-05-16 18:11:02.069398272 +0200
@@ -24,7 +24,7 @@
#
Name: rubygem-regexp_parser
-Version: 2.3.1
+Version: 2.4.0
Release: 0
%define mod_name regexp_parser
%define mod_full_name %{mod_name}-%{version}
++++++ regexp_parser-2.3.1.gem -> regexp_parser-2.4.0.gem ++++++
++++ 3593 lines of diff (skipped)
