Skip to content
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

BUG: clicking on notification link after adding a track leads to /u/undefined #61

Closed
adrienjoly opened this issue Jul 15, 2017 · 1 comment
Assignees
Labels
Projects

Comments

@adrienjoly
Copy link
Member

=> failing acceptance test:

"adding a track -- should show the post on the user's profile after clicking the link"

hypothesis:

  • could be caused by a failure in the models/track.js file that mutates the post object (supposed to contain the uId property)
  • could be caused by failure in the models/algoliaSearch.js file that mutates the post object (supposed to contain the uId property)
@adrienjoly adrienjoly created this issue from a note in Development (📓 Backlog / Next) Jul 15, 2017
@adrienjoly adrienjoly moved this from 📓 Backlog / Next to 🏃‍ In progress in Development Jul 15, 2017
@adrienjoly adrienjoly added the bug label Jul 15, 2017
@adrienjoly adrienjoly self-assigned this Jul 15, 2017
@adrienjoly
Copy link
Member Author

adrienjoly commented Jul 15, 2017

problem found and fixed in commit c6e001b.

it was caused by a breaking change in mongodb driver’s returned object (cf migration to mongodb driver v2, #54): the saved data object is now stored as the first element of a ops array property, instead of being returned directly. (see my comment on mongodb driver's upgrade guide)

=> all calls to insert(), update() and save() should be checked and fixed, after adding failing acceptance tests for the corresponding user actions. => #62

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development
  
🌲 In production
Development

No branches or pull requests

1 participant