Frederick Polgardy

Experiencing the same issue in jscodeshift, and tracked it down to here as well. I'm trying to do a camel case rename, and I've got: ```typescript const p = new...

This is the way you treat a personal itch-scratching project, not a project that other people depend on.

> I’m pretty sure PEG.js community shares the concerns expressed above and would appreciate an honest answer. More than two months, and still no answer?

This is a disaster. Can the community take this project back and fork it?

Doing more research on this today. As described above, `from __future__ import annotations` makes **EVERYTHING** a `ForwardRef` — even primitives, builtins, and things that are actually imported in the module....

Actually, we don't even need to consult the model type registry in a separate step, if we just dump the contents of the registry into the namespace as well. Then...

Ok, reading [this](https://peps.python.org/pep-0649/) now, and it pretty much describes all the pain I'm having trying to get this to work. :) I think I may revert all our future annotations...

I'm definitely not suggesting trying to implement the PEP-649 approach yet... but it does seem like the community is going to be moving in that direction, so I'm hesitant to...

Just bumping this to see where things are. I'm also using a fork of `graphene-sqlalchemy-filter` with some patches, including a small change to address the latest conversion refactor, but would...

> I'm realizing that `graphene-sqlalchemy-filters` handled pagination, while this does not - any guidance for a recommended strategy for implementing pagination using these filters? Why would pagination not work if...