Strange problem with IgniteStarter and RegexBuilder about ignite HOT 2 CLOSED

I think this happens because /./ is considered a "bare slash regex", which needs to be explicitly enabled. If you read the Source Compatibility entry for this change you'll see they enabled #/......../# immediately because it wouldn't break anything, but then hid /......../ behind a feature flag. I guess that flag is enabled by default in Xcode!

Anyway, solutions:

1. Use #/......../# for your regular expressions. You'll see this is what Ignite does elsewhere.
2. We could enable the feature flag, although given that this will be enabled by default in the upcoming Swift 6 this wouldn't have a particularly long life.

Does that help?

from ignite.

Hi Paul,

Yes that does fix it. Thanks for that - I would never have figured it out for myself.

I’ve been enjoying Ignite very much - it works great!

from ignite.