belt | A handful of tools for PHP developers | Functional Programming library

There is no deleteNinja prop in Ninjas component.

Change code like below:

I think you can simply use margin:auto on the second item and your 1em margin on the last item:

"useState. Pretty sure this is for the DOM and not simple flags."

You're definitely wrong on this. It's for any small or large bit of data that you want to persist between renders.

And in general you want to avoid directly referencing DOM elements if you can at all avoid it. You probably don't need to for the vast majority of simple things.

In a React functional component, the entire function is executed anytime a re-render happens.

That fact has some consequences. The most important of which is that any variable declaration in your component is redeclared in a brand new scope on each render.

That means if you do:

I think that can be your ngValue, that need to be changed to:

I found that by adding the following above the WordPress HTACCESS directives resolved the issue:

In the PERFOM UNTIL... loop, you are reading BASEBALL-FILE-OUT, instead of the sorted BASEBALL-FILE-SORTED.

ARE-THERE-MORE-RECORDS = 'NO' is still true from its use in the input procedure. At the beginning of the output procedure, insert MOVE 'YES' TO ARE-THERE-MORE-RECORDS. You also need to replace the READ BASEBALL-FILE-IN with RETURN SORT-FILE, add some fields to SORT-RECORD, and use those fields for the report.

Why do you have BASEBALL-FILE-UNSORTED-IN? It doesn't have any of the fields you need to move to SORT-RECORD.

If you want to use BASEBALL-FILE-UNSORTED-IN, then don't use an input procedure. Instead change the SORT statement from INPUT PROCEDURE 120-SORT-INPUT-PROCEDURE to USING BASEBALL-FILE-UNSORTED-IN. Do not OPEN or CLOSE the file. That will be done by the runtime. Remove the 120- and 130- paragraphs.

Comment everything associated with BASEBALL-FILE-IN, except 01 BASEBALL-RECORD-IN and its data items. That effectively allows the BASEBALL-RECORD-IN data definition to be used as a replacement for SORT-RECORD. That reduces the number of changes that are needed.

SORT is not being used correctly. The report is being printed in 120-SORT-INPUT-PROCEDURE using the fields from BASEBALL-RECORD-IN. It should be printed in 130-SORT-OUTPUT-PROCEDURE using the fields from SORT-RECORD.

Furthermore, no records are sorted because there is no RELEASE statement in the input procedure. To access records after the sort, a RETURN statement is used in the same manner as a READ statement for a sequential file.

The input procedure should be used to move the data from selected records to the sort record, after which the record is released to sort.

The output procedure may then used to produce a report from the sorted data by returning and printing each record until the there are no more sorted records.

Visibility is specified in module signatures (as are type annotations, typically), not on the definitions themselves. You also don't need constructors, but should instead either make the type abstract, or the type alias private.

You can specify a module signature on a local module, as shown below, but typically you'd put it in a .resi ("interface") file. Everything you can put in a module signature you can also put in an interface file. See the docs for more.

This is how I would do it: