Feature: Make env search maintain provided order

[rbingham]

WHAT

Keep order of envs provided by config.

WHY

Env files provided in config are ordered by character length. This causes envs with longer names to be ordered first (This includes folder names). When providing multiple env files to Hurl, the order provided is important as the right most files overwrite duplicate values in left most files. This means that variables in files with shorter names will always overwrite variables in files with longer names. Example:

require("hurl").setup({
  env_file = {
    'env-10.env',
    'env-1.env',
  },
})

# env-1.env
FOO=bar

#env-10.env
FOO=baz

#test.hurl
GET https://example.com/{{FOO}}

The above setup and files will generate this command hurl --variables-file env-10.env --variables-file env-1.env test.hurl which would execute this request https://example.com/bar.

With my changes, the above would generate this command hurl --variables-file env-1.env --variables-file env-10.env test.hurl which would execute this request https://example.com/baz

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• Linter
• Tests
• Review comments
• Security

[changeset-bot]

⚠️ No Changeset found

Latest commit: 51247db

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sweep-ai]

Apply Sweep Rules to your PR?

• Apply: All docstrings and comments should be up to date.
• Apply: Commit messages should be descriptive and provide a clear explanation of the changes made.
• Apply: Author names should be consistent and use proper formatting.
• Apply: Code should be properly formatted and follow a consistent style guide.
• Apply: There should be no unnecessary whitespace or trailing spaces in the code.
• Apply: Variable and function names should be meaningful and descriptive.

This is an automated message generated by Sweep AI.

[jellydn]

LGTM! Thanks, @rbingham

[jellydn]

@all-contributors add @rbingham for code.

[allcontributors]

@jellydn

I've put up a pull request to add @rbingham! 🎉