[FR] Changes in linking places to dates & times

[wesleylancel]

Is your feature request related to a problem? Please describe.

I've recently started using TRIP to plan my summer holiday, thanks for your work on it! I'm running into some things that I think can be improved around the linking of a place to day(s) of a TRIP.

1. There's no way to set an end time.
2. There's no way to mark something as "all day".
3. When a place is linked to multiple days these are individual "links" afterwards. When you then want to change something, you need to do it on all individual days (for example booking status). Also, when you've entered a price on the place, it is simply copied to every linked day, which doesn't make sense for accommodations for example.

Describe the solution you'd like

1. Set a separate start and end date on a link and keep it as one link.
2. Allow setting and end time on a link.
3. Allow marking a link as all day.

Additional context

No response

[wesleylancel]

@itskovacs Any feedback on this one? I'd be willing to look at implementing (some of) this myself, but would like your feedback on the approach before starting.

[sjorge]

Some of this hase been covered in issues or FR's (often where I was the creator 😅 of said questions/bugs)

There's no way to set an end time.

Add 2 planned items one for the start and one for the end time (There is a duration field on a place but not on a plan item, which is a bit confusing IMHO), personally I just add the expected duration in the comment field on the first line.

There's no way to mark something as "all day".

Indeed there is not, I did describe something that might be generic enough to cover this usecase in the Add Hotel FR.
#148 (reply in thread)

When a place is linked to multiple days these are individual "links" afterwards. When you then want to change something, you need to do it on all individual days (for example booking status). Also, when you've entered a price on the place, it is simply copied to every linked day, which doesn't make sense for accommodations for example.

Yeah, I'll be lying if I did not do a backup, sed on backup file, restore in recent past 😓

Would be nice if you add a plan to multiple days it would stay as one, not be created multiple times in the background. Although the later probably keeps implementation simple and that's why it's currently like this.

[wesleylancel]

@sjorge Thanks for the reply! I'm all for keeping things simple, but the "workaround" here isn't very pretty in my opinion, and all of my trips have multi-day accommodations that I edit multiple times while planning the trip.

Adding and end date with time and an all-day flag (like pretty much any calendar has) would solve all of these problems in my opinion.

[itskovacs]

Out of context as I'll read the topic tonight but to your message @wesleylancel :

that I edit multiple times while planning the trip

There is an option to bulk edit your plans 👍

[itskovacs]

Hi again 👋,

Apologies for the delay; I confused this thread with discussion #155.
TRIP follows a double-entry logic similar to accounting software. This requires users to create separate plans for the start and the end so they can have distinct properties. While I recognize this structure is debatable, it is a deliberate design choice for the application.
Changing this would require rewriting a lot of the backend and logic, so it's not feasible at the moment.