https://supertokens.com/ logo
Channels
Powered by
#support-questions
  • r

    rp

    02/02/2022, 5:22 AM
    Makes sense.
  • b

    bill92

    02/02/2022, 5:22 AM
    oh it worked this way
  • r

    rp

    02/02/2022, 5:22 AM
    ah cool!
  • b

    bill92

    02/02/2022, 5:22 AM
    connectionURI: 'http://supertokens:3567'
  • r

    rp

    02/02/2022, 5:22 AM
    haha ok!
  • b

    bill92

    02/02/2022, 5:22 AM
    awesome! this is really exciting 😄
  • b

    bill92

    02/02/2022, 5:22 AM
    thanks man
  • r

    rp

    02/02/2022, 5:22 AM
    awesome!
  • g

    gadi

    02/02/2022, 10:00 AM
    Sure, for now I fixed it by patching apollo-server-express as following:
    Copy code
    diff --git a/dist/ApolloServer.js b/dist/ApolloServer.js
index 203eef5bc362cf6ed46933726b08c6aeb2cf7277..3cf2d07e6a60c534cf5dd56b29c119a0d032071a 100644
--- a/dist/ApolloServer.js
+++ b/dist/ApolloServer.js
@@ -80,6 +80,9 @@ class ApolloServer extends apollo_server_core_1.ApolloServerBase {
                 query: req.method === 'POST' ? req.body : req.query,
                 request: (0, apollo_server_core_1.convertNodeHttpToRequest)(req),
             }).then(({ graphqlResponse, responseInit }) => {
+                if (res.headersSent) {
+                    return;
+                }
                 if (responseInit.headers) {
                     for (const [name, value] of Object.entries(responseInit.headers)) {
                         res.setHeader(name, value);
@@ -96,6 +99,9 @@ class ApolloServer extends apollo_server_core_1.ApolloServerBase {
                 if (!(0, apollo_server_core_1.isHttpQueryError)(error)) {
                     return next(error);
                 }
+                if (res.headersSent) {
+                    return;
+                }
                 if (error.headers) {
                     for (const [name, value] of Object.entries(error.headers)) {
                         res.setHeader(name, value);
  • r

    rp

    02/02/2022, 10:22 AM
    I see. That makes sense!
  • e

    extremelf

    02/02/2022, 12:04 PM
    is it possible do add fields to the saved user, for example in my signup function I'm calling an internal api and it returns a value, is it possible to append that as an extra column in the database where users are saved?
  • r

    rp

    02/02/2022, 12:11 PM
    @User that's not possible at the moment. We are working on that though. For now, you have the following options: - Save that field in your own db against the userId returned by supertokens; and / or - Save that info in the session for the user
  • e

    extremelf

    02/02/2022, 12:16 PM
    ok, thanks!
  • b

    Bruno Diferente

    02/02/2022, 12:16 PM
    Hello there,
  • r

    rp

    02/02/2022, 12:24 PM
    Hey @User !
  • b

    Bruno Diferente

    02/02/2022, 12:42 PM
    Had a question in mind but thought reading docs before asking
  • r

    rp

    02/02/2022, 12:42 PM
    fair! thanks
  • b

    bill92

    02/02/2022, 9:11 PM
    Hello, are there any guides on how to use supertokens with the passwordless, but just the session management side of things and build custom UI? Pretty much all we need is the backend and core.
  • p

    porcellus

    02/02/2022, 9:13 PM
    Hi, you could just skip initializing the passwordless recipe on the frontend and follow the same guide otherwise.
  • p

    porcellus

    02/02/2022, 9:13 PM
    also, you can override all of the frontend components provided, so that may serve your needs as well.
  • b

    bill92

    02/02/2022, 9:14 PM
    override them completely or just add styles upon them?
  • p

    porcellus

    02/02/2022, 9:15 PM
  • b

    bill92

    02/02/2022, 9:16 PM
    I assume 
    props
    has all of the metadata need to build own UI? inputs id, names, values, etc?
  • p

    porcellus

    02/02/2022, 9:19 PM
    depends on which component you want to override, but in general it has everything: we are using the same props to implement them
  • b

    bill92

    02/03/2022, 12:32 AM
    so, you are not rendering the 
    <DefaultComponent {...props}/>
    ? You are pretty much injection props in a whole new component?
  • b

    bill92

    02/03/2022, 12:49 AM
    currently brainstorming
    Copy code
    ts
components: {
          PasswordlessUserInputCodeForm: () => {
            // logic here to enter the OTP and send it to the backend
            return <div></div>;
          },
          PasswordlessPhoneForm: ({ config, recipeImplementation }) => {
            const [phoneNumber, setPhoneNumber] = useState<string>("");
            return (
              <form
                onSubmit={async (e) => {
                  e.preventDefault();
                  window.alert(phoneNumber);
                  const isInvalid = await config.validatePhoneNumber(
                    phoneNumber
                  );
                  if (!isInvalid) {
                    // do something here, send the code
                  }
                }}
              >
                <label>phone number</label>
                <input
                  type='text'
                  value={phoneNumber}
                  onChange={(e) => setPhoneNumber(e.target.value)}
                />
                <button type='submit'>Send Code</button>
              </form>
            );
          },
        },
  • r

    rp

    02/03/2022, 5:26 AM
    @User something like that could work. Yea
  • b

    bill92

    02/03/2022, 5:31 AM
    Thanks!
  • s

    scherbatsky.jr

    02/03/2022, 8:34 AM
    Hello all, I am on a project to using Vue 3 and Nest js to support multi tenancy. As the docs are not ready for multi tenancy and examples seem to only for react frontend, has someone worked on similar stuff before? Or could point me to examples? Thanks!
  • r

    rp

    02/03/2022, 9:54 AM
    hey! We don't have multi tenancy support yet 😦 Whilst you can use us with vue (by calling our APIs directly from the frontend), im not sure the multi tenancy use case can be fulfilled at the moment - but it also depends on what you want. There can be a hacky solution to it. What is your multi tenancy use case?
1...199200201...343Latest