Add support for testing whether a value is a constant-cased string

[Pranavchiku]

Resolves #534.

Checklist

• Add readme.md
• Add package.json
• Add lib
• Add examples
• Add docs
• Add etc
• Add bin
• Add benchmark
• Add test

---

@kgryte

[Pranavchiku]

I don't have the access to add assignees for the PR :/

Edit: Thanks :)

[kgryte]

@Pranavchiku Sorry about that. This is the first time I'm trying this out. Just assigned. Let's see what happens.

[kgryte]

Looks like the workflow is stuck in a queue, so we'll need to wait a while for it to kick off. How long we'll have to wait is TBD.

[Pranavchiku]

Looks like the workflow is stuck in a queue, so we'll need to wait a while for it to kick off. How long we'll have to wait is TBD.

It might get failed if stuck there for long time ( I faced this issue once at lfortran )

[Planeshifter]

Okay, so there are currently problems with the AI scaffolding workflow when triggered from a fork, which we will need to look into. Apologies!

As a temporary workaround, I have created a assert/is-constantcase branch with your README.md and the files: #541

Feel free to either checkout that branch or copy the files over into this PR's branch.

[Pranavchiku]

I rebased it over my PR, and added implementation, made a clean build again, there are quite a few bugs like output not correctly predicted, linting errors, and a few things will be needed to fix before I can push those changes in this PR, will try to get that done as soon as possible :)

[kgryte]

Thanks for trying this out @Pranavchiku!

[Pranavchiku]

Sorry for delaying it, will try to get the things up as soon as possible.

[Pranavchiku]

so,

tape( 'the command-line interface supports use as a standard stream', opts, function test( t ) {
	var cmd = [
		'printf "BEEP\nboop"',
		'|',
		EXEC_PATH,
		fpath
	];

	exec( cmd.join( ' ' ), done );

	function done( error, stdout, stderr ) {
		if ( error ) {
			t.fail( error.message );
		} else {
			t.strictEqual( stdout.toString(), 'true\ntrue\n', 'expected value' );
			t.strictEqual( stderr.toString(), '', 'does not print to `stderr`' );
		}
		t.end();
	}
});

This test is not passing in test.cli.js, idk the reason, pasting the logs below

  the command-line interface supports use as a standard stream


    ✖ expected value
    -----------------
      operator: equal
      expected: 'false\nfalse\n'
      actual:   'false\n'
      at: done (/home/pranavchiku/stdlib/lib/node_modules/@stdlib/assert/is-constantcase/test/test.cli.js:179:6)

    ✔ does not print to `stderr`
    ```

[kgryte]

@Pranavchiku Left a comment. You may need to merge in changes from upstream. Currently, this PR is a bit "dirty" in that it contains changes/files which are already present in the upstream repo.

[Pranavchiku]

Yeah I will do that.

[Pranavchiku]

I observed few things on the files created by stdlib-bot

1. Ending the file with two extra lines
2. Using extra line after use-strict
3. Tests logic are not great
4. test/fixtures file is not created

Rest everything was very perfect!

[kgryte]

@Pranavchiku That's great feedback! Thanks! cc @Planeshifter

[Pranavchiku]

I am currently getting a small error in test.cli.js, I will resolve that, polish the PR and then push changes as soon as possible :)

[kgryte]

@Pranavchiku Awesome! Thanks for working on this!

[Pranavchiku]

@kgryte you can have a final review.

[kgryte]

LGTM. Thanks, @Pranavchiku!

[Planeshifter]

I observed few things on the files created by stdlib-bot

1. Ending the file with two extra lines
2. Using extra line after use-strict
3. Tests logic are not great
4. test/fixtures file is not created

Rest everything was very perfect!

Thank you @Pranavchiku for the feedback. 1., 2., and 4. will be fixed in the next iteration of the scaffolding tool. We will keep iterating to hopefully get to a very smooth development experience in the near future.