fix: cannot save nullish values for required fields

[RaschidJFR]

Fixes #1980

New Pull Request Checklist

• I am not disclosing a vulnerability.
• I am creating this PR in reference to an issue.

Issue Description

Related issue: #1980

Approach

Instead of checking for value being nullish (eg !value), check for it being different from null and from empty string ('')

TODOs before merging

• Add tests
• Add changes to documentation (guides, repository pages, in-code descriptions)
• A changelog entry is created automatically using the pull request title (do not manually add a changelog entry)

[parse-github-assistant]

Thanks for opening this pull request!

• ❌ Please edit your post and use the provided template when creating a new pull request. This helps everyone to understand your post better and asks for essential information to quicker review the pull request.

[RaschidJFR]

I'm having trouble creating the tests for BrowserCell. Jest failed for imports using double quotes (") instead of single quotes ('). I tried a couple of things by changing the regex in preprocessor.js, but no luck.

So I proceeded to lint-fix all files... should I do it in this PR?

[mtrezza]

So I proceeded to lint-fix all files... should I do it in this PR?

Uh, please in an extra PR, to make it easier to review the 2 PRs.

[mtrezza]

Looks good! Is this ready for merge?

[RaschidJFR]

It is ready, but for the record, when the changes in #2004 are applied, the test here created will fail:

 FAIL  src/lib/tests/BrowserCell.test.js

  ● Test suite failed to run

    Jest encountered an unexpected token

    This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.

    By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".

    Here's what you can do:
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/en/configuration.html

    Details:

    /Users/raschidjfr/Documents/git/github/parse-community/parse-dashboard/node_modules/react-popper-tooltip/dist/styles.css:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){.tooltip-container {
                                                                                             ^

    SyntaxError: Unexpected token '.'

      1 | import React from 'react';
      2 | import { usePopperTooltip } from 'react-popper-tooltip';
    > 3 | import 'react-popper-tooltip/dist/styles.css';
        | ^
      4 |
      5 | const PopperTooltip = (props) => {
      6 |   const { children, tooltip, visible, placement } = props;

      at ScriptTransformer._transformAndBuildScript (node_modules/@jest/transform/build/ScriptTransformer.js:537:17)
      at ScriptTransformer.transform (node_modules/@jest/transform/build/ScriptTransformer.js:579:25)
      at Object.<anonymous> (src/components/Tooltip/PopperTooltip.react.js:3:1)

Test Suites: 1 failed, 15 passed, 16 total
Tests:       61 passed, 61 total
Snapshots:   0 total
Time:        5.623s
Ran all test suites.

As the failure is not directly related to this PR, I think it would be a good idea to merge this now and address the problem in #2004 .

[mtrezza]

Sounds good

[parseplatformorg]

🎉 This change has been released in version 4.0.0-alpha.9

[parseplatformorg]

🎉 This change has been released in version 4.0.0-beta.3

[parseplatformorg]

🎉 This change has been released in version 4.0.1