feat: Update constructor judgments of LLRT

[nabetti1720]

In LLRT, this corresponds to the following message that occurs in the execution of the constructor of an object that requires one or more arguments.

See also. unjs/runtime-compat#126

      {
        "name": "api.Request.Request",
        "info": {
          "code": "bcd.testConstructor('Request')",
          "exposure": "Window"
        },
        "result": null,
        "message": "threw TypeError: Error calling function with 0 argument(s) while 1 where expected"
      },

Execution results in LLRT (cli mode):

% ./llrt -v                              
LLRT (darwin arm64) 0.1.14-beta

% ./llrt -e "const req = new Request();"                     
TypeError: Error calling function with 0 argument(s) while 1 where expected
    at <eval> (eval_script:1:13)

[nabetti1720]

Hi @queengooborg . Is the signed Commit working?

[Elchi3]

Hey @nabetti1720, looks like it didn't work unfortunately.

If it is verified you would see "verified" with the commit. See for example https://github.com/openwebdocs/mdn-bcd-collector/pull/1487/commits.

[nabetti1720]

Hey @nabetti1720, looks like it didn't work unfortunately.

If it is verified you would see "verified" with the commit. See for example https://github.com/openwebdocs/mdn-bcd-collector/pull/1487/commits.

Thanks for the confirmation.
I did confirm that it was indeed Verified✅ on the first commit. However, when I rebase from the GitHub website, it seems to have been removed at some point...

[Elchi3]

Ah interesting, I see this is being talked about in the docs: https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification#signature-verification-for-rebase-and-merge. GitHub recommends to "rebase and merge locally, and then push the changes to the pull request's base branch."

[nabetti1720]

Ah interesting, I see this is being talked about in the docs: https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification#signature-verification-for-rebase-and-merge. GitHub recommends to "rebase and merge locally, and then push the changes to the pull request's base branch."

Hi @Elchi3 , Thanks for the information.

I have force pushed the local content again.
Now you can see that my commit has a Verified icon on it.

Do I need to rebase from this state? If you can confirm that my commit is verified, can you rebase and merge it on the maintainer's side?

[Elchi3]

Thank you @nabetti1720, this looks good to me. 👍
Congratulations on your first merged pull request in this project! 🎉