Barne Kleinen

If you have a look at the Moment Documentation, it is already included: https://momentjs.com/docs/#/displaying/format/ Week of Year | w | 1 2 ... 52 53   | wo | 1st 2nd...

Issue: https://github.com/teamcapybara/capybara/issues/2772

From my understanding, Capybara already uses the replacement if the methods have been removed: if @browser.respond_to? :session_storage @browser.session_storage.clear else ... call js methods directly -> thus, I see no need...

this fixed it for me in rails: ``` driven_by :selenium, using: config.driver, screen_size: [1400, 1400], options: config.driver_options do |driver_option| driver_option.add_argument('--disable-search-engine-choice-screen') end ```

I'll give it a shot.

while adapting the test cases I noticed that not all three upcoming tasks are retrieved by "upcoming". Both cancelled and completed tasks are shown in my upcoming view:

> I can't reproduce that on my end. Is it because of this default setting? yes. as soon as the manualLogDate is after the completion, they are no longer shown....

So, I've started working on this (see closed PR [145](https://github.com/thingsapi/things.py/pull/145)) but before I go on, I need some clarification: ## 0. Naming: in the db, there are **templates** for recurring...

After some more digging, I think only the _nextInstanceStartDate needs to be considered: ## repeat templates | title | start | startDate | rt1\_repeatingTemplate | rt1\_instanceCreationStartDate | rt1\_instanceCreationPaused | rt1\_instanceCreationCount...

Note: the field **rt1_recurrenceRule** is readable in DataGrip, this one is from _Created as non-repeating, repeat added later_: ``` ed 64092211200 fa 1 fu 256 ia 1757203200 of wd 0...