Description of problem:

The command "file" applied to a JSON file now outputs "JSON data", without
including the string "text" in the output. Earlier versions behaved differently,
and this is also contrary to the documentation of file (man file), which states

     The type printed will usually contain one of the words text (the file
     contains only printing characters and a few common control characters and
     is probably safe to read on an ASCII terminal), executable (the file con‐
     tains the result of compiling a program in a form understandable to some
     UNIX kernel or another), or data meaning anything else (data is usually
     “binary” or non-printable).  Exceptions are well-known file formats (core
     files, tar archives) that are known to contain binary data.  When modify‐
     ing magic files or the program itself, make sure to preserve these
     keywords.  Users depend on knowing that all the readable files in a di‐
     rectory have the word “text” printed.  Don't do as Berkeley did and
     change “shell commands text” to “shell script”.

Apparently file has now done as Berkeley did...

Version-Release number of selected component (if applicable):

file-5.39

How reproducible:

Steps to Reproduce:
1. Create a file with JSON contents, eg.

{
	"a": 1,
	"b": 2
}

2. Apply the command file to it.

Actual results:

$ file foo.json 
foo.json: JSON data

Expected results:

Output should contain "text" somewhere (it could contain also "JSON").
Eg. on CentOS 6 file returned just "ASCII text" for this file.
The change broke a script that used "file" to find plaintext files.