• r

    rp

    2 years ago
    Which is also written by us. So you don’t need to worry about it
  • r

    rp

    2 years ago
    @tredstone in the new version, it wouldn’t be. However we will implement different measures to ensure misuse like @HyperGo18 mentioned does not happen, or is blocked.
  • tredstone

    tredstone

    2 years ago
    how do we submit feature requests? i think it would be nice to have a hook taht would let you change the jwt payload during a token refresh
  • r

    rp

    2 years ago
    Hmm. That’s an interesting feature indeed. You can create an issue about this or implement it yourself and create a pull request 😀
  • tredstone

    tredstone

    2 years ago
    i think i just might, lol
  • tredstone

    tredstone

    2 years ago
    i'm curious to hear some feedback from others on that idea as well
  • r

    rp

    2 years ago
    I’ll think about this a bit more and let you know my thoughts!
  • HyperGo18

    HyperGo18

    2 years ago
    by the way, are there any plans for a version written in go?
  • r

    rp

    2 years ago
    Not yet. We are actually building a version that is slightly better to develop on - right now a problem is that if we want to support 5 frameworks with 5 databases, we have to write a total of 25 repos! And that’s just really difficult to do and maintain. So we are creating a version that has decoupled the framework part from the database part (using a micro service kind of an architecture). If you are currently using the node version, then moving to this new version should not be too much of an issue. And creating go Lang support for this new version will be FAR easier than doing it now.
  • r

    rp

    2 years ago
    This new version should be available sometime within the next month