hillin

Here is another example: for the input `1234\n5678`, I'd expect it to be tokenized as: | Token | Expected Range | Current Range | | ----------- | ----------- | -----------...

> This still seems to me like the ideal solution is to use inclusive ranges To me exclusive ending index is still the legitimate way to go. We just need...

> The mark method already does this Oops, I've missed that one. > I would certainly review the PR if you want to work on it. I'll see what I...

I think what @HofmeisterAn actually mean is https://github.com/dotnet/Docker.DotNet/blob/f58748616cc5b679b25496926c5688294c94d850/src/Docker.DotNet/Models/HostConfig.Generated.cs#L211

`lookahead` is definitely something we missed from Parsimmon. It is quite useful especially when you want to match invalid content (for skipping syntax errors and keep parsing): ```typescript const op...

e.g. ```typescript // without flatten bnb.text('1').and(bnb.text('2')).and(bnb.text('3')).parse('123') // => [["1","2"],"3"] // the nested array is obviously hard to deal with // with flatten bnb.text('1').and(bnb.text('2')).and(bnb.text('3')).flatten().parse('123') // => ['1', '2', '3'] ```

Hi! It's because we are trying to upgrade to Angular 18(rc3), which requires Typescript 5.4+. It's just an experiment and we can definitely wait for ABP 8.3.

I've got a working implementation. Since I suppose there should be some magnitude of rework/refactor to the sheet component to be done in order to get this properly implemented, I'm...

Welcome back! You don't see a hibernated repo revives every day 😉

@sumeyyeKurtulus I believe `required` is only for reference types. For value types (numbers, enums and structs) they should always be generated as non-nullable - unless they are declared as `Nullable`,...