Overuse of "atSource" boolean var (and more)

[louisgreiner]

At some places in the code, we use atSource (boolean) to deal with source/target expected behaviors. However, this can lead to misunderstanding when the return type of a method should return a boolean as well.

For example:
https://github.com/OpenRailAssociation/netzgrafik-editor-frontend/blob/52e468b2149e31592cd8d2787f227a92ef248de9/src/app/view/editor-main-view/data-views/trainrunsections.view.ts#L2022-L2026C11

  private filterTimeTrainrunsectionNonStop(
    viewObject: TrainrunSectionViewObject,
    atSource: boolean,
    isArrival: boolean,
  ): boolean {

I don't know what should be done

[aiAdrian]

The method is really complicated to read. I see the point. I can be written more clear and with better readability.

[louisgreiner]

It is more like, we use a lot of boolean values to do either something either something else. Maybe the condition should be bore by something else that a boolean parameter in the method, because this weigh down the code (and not only in this place, this issue is more global!)