-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Major updates and refactors #12
Conversation
apiBase: 'http://localhost:8888/v0/', | ||
apiBase: 'https://api.openframe.io/v0/', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jvolker Notice this — this points the local dev web app at the production api. If/when we get the API server running locally again we should switch this default back.
Might be better long-term to move these settings to env vars.
@@ -112,41 +127,42 @@ class App extends Component { | |||
{ | |||
//<Notification notice={ ui.notice } updateNotification={actions.updateNotification}/> | |||
} | |||
<Notifs /> | |||
{/* <Notifs /> */} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This Notifs
(from redux-notifications
) wasn't easy to just update along with the other deps... we'll need an alternative, to fork and update this package, or to roll our own little notifications lib.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the exact functionality we would be loosing with this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is that all notifications outside overlays?
What's the problem with redux-notifications
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is for the success/info/error notifications for the UI (not the error warnings in edit forms).
I don't remember exactly what the error was, but think it hasn't been updated to work with the latest versions of react and/or redux. Maybe be that we can fork and update it or find another comparable package.
@jvolker As I mentioned in slack, don't worry too much about reviewing this in detail. It's WAY too big of a PR to review in a comprehensive way, and I don't plan on releasing this version until it's well tested, so I imagine there will be a number of bug fix and update PRs after this before we'd release this code. |
Thanks so much for this big update @jmwohl. I'm going to do review it later. I can already confirm that I can run this locally without errors using |
const open = require('open'); | ||
|
||
let server = new WebpackDevServer(webpack(config), config.devServer); | ||
|
||
server.listen(config.port, '0.0.0.0', (err) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a particular reason why you hardcoded the port?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope! I don't remember why I did that, and there's no reason it can't come from the config. I'll update that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Realized this file isn't actually used, removed it.
Remove duplicate comment.
Editing artwork and saving it without a name crashes the website and throws this error:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I skimmed the code as requested and ran the app to test manually for errors:
- browse public and private channels (multiple artwork formats incl. shaders)
- adding artwork
- editing artwork
- deleting artwork
- edited frame
- deleting frame
I've found a bug when editing artwork and added a few more comments.
Again, thanks a lot for this massive update!
Closes #5 |
I fixed the artwork edit error, but there's definitely more work to do on normalizing our error handling in the UI. |
Alright, I decided to just pull the |
Great, thanks for your work! I opened #15 to continue the conversation about notifications/alerts there. |
I've just tested this and it's still an issue for me. I've tested with artwork "5e449d86a38167076035c032". |
Known issues: