Closed holingpoon closed 6 years ago
Fix the merge conflict and try to fix the tests too. The broken tests are not related to your work, but they should still work given your update.
@ktp242 eslint complains about the trailing comma because it's a list. It doesn't matter if it's an array and there's a list there, or if they're function params, they're still lists.
@EdwinGuzman So should there be commas after the last item? Should they stay off for best practices?
If we're following eslint, yes, the commas should be there. Also, the local import statements should not have an extension at the end (jsx
, js
);
Okay, @ktp242 @EdwinGuzman I kept the trailing commas. I also removed .jsx
extensions from the import
statements.
I remember once I ran into a broken function because a trailing ,
attached to the arguments. Just want to make sure it doesn't break anything.
@ktp242 That is also my concern, localhost
seems to be tolerant of trailing commas right now. Maybe deploying to development
will give us better clues?
When you deploy, the app will be serving the translated and compiled JS which will remove the commas I think (when babel does the transpilation). Locally, the app is serving the jsx files so if it works locally then it should work when deployed, but it's go to check either way.
Works well.
Will work with @ktp242 on resolving conflicts in
monthData.js
, and figure out branch merging scheme. Thanks!