Find trips about backpacker HOT 8 OPEN

@kensupermen I will do it.

from backpacker.

@sabinahofmann Okey man. If you can use reactjs, I hope you implement it to improve performance

from backpacker.

I am rather a backend developer and would be set up the logic up to view.
I can see in migration, you build a has_many association: a user can have one or more trips. It's that right? According to which criterias can a user find trips?

from backpacker.

@sabinahofmann Yes, That right. The user can find trips in the future. And trips not duplicate time with trips that user registed.
Example:

Trip1 start_at 8 Dec 2017
Trip2 start_at 9 Dec 2017
Trip3 start_at 9 Dec 2017

User registed trip3, so user only see trip1
That is my idea, so if you have any idea better, we will discuss and make it better.
Btw, I want to a feature done mean this feature has backend and fronend, because this application is a web, not a api.

from backpacker.

I understand you. But I'm not good as a frontend developer and my intuition wasn't to make an api. Wouldn't it be more effective if someone makes the view, who is also good at it - especially in React?

from backpacker.

@kensupermen How about I split the whole thing into two pull requests. With React the data is transferred as JSON, so the first PR would be the backend logic with the output of the data as JSON and the second part would be the React part. This part can then either be taken over by me or someone else who can do it better.

from backpacker.

@sabinahofmann Ok, fine. If you don't know about reactjs, I think you know about html and css. I want it has basic front end (html, css, bootstrap), don't need reactjs. We will convert later. Because this function in backend every easy, so I want html look cool

from backpacker.

@kensupermen the pull request for this feature or rather task : #14

from backpacker.