Tarrgon
Tarrgon
I've found a flaw in the parsing of using both operators. Something that I didn't consider since the current syntax doesn't support it, either. Using both OR and NOT on...
I think this fixes it
> I still hate syntax changes.. I think it should be backwards compatible, at the least Which is why this is an optional change. If I made it backwards compatible,...
> Does r34 use Elastic and opensearch? Couldn't tell you, I designed it off of what I personally believe to be the most readable syntax. Which to me includes separating...
> May I suggest a more conventional format? Something like `~(tagA tagB)` would return results with either tagA OR tagB. > It would match your existing negation pattern. There's 2...
I've converted this back to draft for the time being as before anything happens to this, it needs major code revision and review, regardless of what the syntax may or...
Closing this because I don't plan on continuing working on this feature anymore, and both the code itself and the format is unacceptable.
Yeah I've gone ahead and made ones with a max length normalize to `\n` as we actually already do this in some places Notably post sources: https://github.com/e621ng/e621ng/blob/master/app/models/post.rb#L350 which normalize `\r\n`...
First, I want to preface this with: I am not a ruby dev. Until like last week, I never put any thought into ruby... ever. However, I implemented this on...
I've opened a draft here for future discussion: https://github.com/e621ng/e621ng/pull/625