DateHelper | A Swift Date extension helper | iOS library

EDIT: Updated question 1 for more clarity.

So, this might be a stupid question, but here we go.

A few months ago, during classes we wrote a simple weather app, with the intent to further develop it.

My questions are:

1. Where and how the function should be called/invoked?
2. How to execute the code, so that the App prints the information received from the two APIs, in the console.
3. Once the information is printed, how it can be manipulated in the front end, like displaying on a simple card?

Here is the main code:

I have a simple report page, and I am using Laravel 7 to build it.

I want to trigger auto-download a PDF with that view.

What would be the most lightweights I should look into? I did a quick Google, and I saw so many options.

I decided to try this and did all the steps, below is my final code

Note this line : $pdf = PDF::loadView('layouts.be.baby.report', get_defined_vars());

Is there way to get time_ago_in_words in different languages, or write locales?

I'm pretty new to iOS dev/Core Data and am having trouble implementing one part of my workflow within my app. See below:

Core Data Properties:

• item

• Attributes: title, amount, date, status, category (rel), note (rel)

• note

• Attributes: title, contents, createdAt, updatedAt, item (rel)

When a user creates a new item, all attributes are required, except for .note as I'd like to give the user the option to create a note at a later time if only needed.

What I want to accomplish:

1. User selects row to display item details
2. On item details view, user selects notes (highlighted in yellow above) to go to Add/Edit notes
3. The note is just a single object that the user can enter/update the note. So basically, one note per item.

MY CODE

Xcode 11.5, Swift 5

I want to sum the attribute amount from my entities and show it but only from the todays inputted data

Here's my entities ExpenseLog Entities

And here's my fetch request to get todays data

I'm having a problem on sum the filtered data using return method from "amount" attribute which have Decimal data type. The error msg like this and have a suggestion to Insert ' as! Decimal' behind the amount but it doesn't help

Cannot convert value of type 'NSDecimalNumber?' to expected argument type 'Decimal'

Here's my code

I have a datehelper table with every YYYY-MM-DD as DATE between the years 2000 and 2100. To this I'm joining a subquery for all unit transactions. unit.end is a DATETIME so my subquery simplifies it to DATE and uses that to join to the datehelper table.

In 5.6 this query takes a couple seconds to run a massive amount of transactions, and it derives a table that is auto keyed based on the DATE(unit.end) in the subquery and uses that to join everything else fairly quickly.

In 5.7, it takes 600+ seconds and I can't get it to derive a table or follow the much better execution plan that 5.6 used. Is there a flag I need to set or some way to prefer the old execution plan?

Here's the query:

Running the following code to create a new Database (PostgreSQL 11.3) row:

I have a class library that is full of typical methods that I use a lot, especially in my domain. Most of this library has remained unchanged for years at this point. More adds than changes.

In the library there's a lot of calling methods within the library - using itself.

From a complete optimization point of view - because this lib is used a lot what makes more sense:

Use methods within the lib or re-write the code within every method to avoid calling into another method. What's the cost of calling another method or maybe two methods deep versus having the code in the called method.

For instance, this illustrates a common scenario. This method turns what's typically an ugly URL parameter (with encoded html) into a more simple, hackable, date with dashes. So it gets called hundreds of times maybe thousands on a page by hundreds of users (so maybe not a trivial amount of times?).

The reason I don't think this is pre-optimization or micro optimization (hence why I'm asking) is that since this is a library and is being used by many applications, on the same server, with 100s of users, the "micro" savings could really add up.