bezkoder/react-jwt-auth

Tables are not created + no communication between front-end & back-end

Ladaht opened this issue · 1 comments

Ladaht commented

Hello, Congrats on making these apps available for the general public.
I downloaded both front-end and backend (Postgresql) but I have the following issues despite following instructions:

Setup for front and back:

  • changed autheader to" return { 'x-access-token': user.accessToken };"

  • bodyParcer is deprected, changed to app.use(express.json()); and app.use(express.urlencoded({extended: true}));

  • register form will not respond on Submit unless I changed he zero in (this.checkBtn.context._errors.length === 0) to 1. Browser link changed but no success message and form still showing.

  • in index.js, changed the FALSE in "operatorsAliases: 0" to ZERO, or removed completely.

  • last;y, added <React.StrictMode> to index.js in front-end, new error below from dev tools:

Warning: Legacy context API has been detected within a strict-mode tree.

The old API will be supported in all 16.x releases, but applications using it should migrate to the new version.

Please update the following components: Button(s), Control(s), Form(t), s

Learn more about this warning here: https://fb.me/react-legacy-context
in Form(t) (at register.component.js:134)
in div (at register.component.js:127)
in div (at register.component.js:126)
in Register (created by Context.Consumer)
in Route (at App.js:135)
in Switch (at App.js:132)
in div (at App.js:131)
in div (at App.js:64)
in App (at src/index.js:11)
in Router (created by BrowserRouter)
in BrowserRouter (at src/index.js:10)
in StrictMode (at src/index.js:9)

IMPORTANT:

The back-end does not create the database and table (db: MY-DATABASE-POSTGRES-NAME, with password)
The front-end shows up fine in the browser but does not communicate with my postgres database. On submit, the register from fields will clear, and ONLY the browser link changed with new data from fields, ONLY when I changed the ZERO in (this.checkBtn.context._errors.length === 0) to 1. which is not a solution.

Is the legacy API warning the root of the problem or should Sequalize create the database and tables regardless?

Rokedd commented

I have the same issue