You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I cloned and run the service on port:3000.
I saw that it tries to save the snippets on port 4000, so I started a json-server with a default db {snippets:[]}.
Snippets entries are created with id 1,2,3... but the code is not present.
I also see this when clicking on visualize which might be related to not being able to save the code:
Warning: Failed prop type: Invalid prop `shareId` of type `number` supplied to `_class`, expected `string`.
in _class (at index.js?entry:182)
in _class (created by Container)
in AppContainer (created by Container)
in Container (created by App)
in div (created by App)
in App
Would be nice to fix this or propose any other back-end for snippets.
FYI: As a workaround I tried to run json-server with shareId as identifier: json-server -p4000 -w db.json -i shareId
In this case, every new snippet is saved on the server when I press visualize.
For some reason I cannot see the share link button, but if I manually get the newly created shareId then I can visualize correctly (e.g. on http://localhost:3000/v/4 )
The text was updated successfully, but these errors were encountered:
I cloned and run the service on port:3000.
I saw that it tries to save the snippets on port 4000, so I started a json-server with a default db
{snippets:[]}
.Snippets entries are created with id 1,2,3... but the code is not present.
I also see this when clicking on visualize which might be related to not being able to save the code:
Current entries on http://localhost:4000/snippets/
Would be nice to fix this or propose any other back-end for snippets.
FYI: As a workaround I tried to run json-server with
shareId
as identifier:json-server -p4000 -w db.json -i shareId
In this case, every new snippet is saved on the server when I press visualize.
For some reason I cannot see the
share link
button, but if I manually get the newly created shareId then I can visualize correctly (e.g. on http://localhost:3000/v/4 )The text was updated successfully, but these errors were encountered: