Improve path resolution

[NejcS]

This makes change to how we resolve path parameters (e.g.: build_folder, log_file_name, conformance_tests_folder).

The main change to the user is that now the parameter path is resolved based on where the parameter was provided:
config.yaml, CLI argument. If parameter is not provided in either of those, the parameter's default value will be relative to the spec file.

Until now some parameters were relative to the config file even if provided as CLI argument (e.g.: conformance-tests-script, log-file-name ...).

[NejcS]

This function is not needed anymore since args.log_file_name is now an absolute path to the file.

[NejcS]

This is not needed anymore since args.log_file_name is now an absolute path to the file.

[pedjaradenkovic]

A couple of todos before we proceed:

• Fix the bug when calling the plain_module from different folder
• Since we are changing tests scripts, we would like to move temporary test folders to temp folders if possible. We can discuss with Vitjan if the paths should be filtered out.

[NejcS]

This will release important improvements to Codeplain's path resolution system that fix Windows compatibility issues and enhance cross-platform support. These changes affect the test scripts included with Codeplain.

• Build folders now go to system temp directory.
• No more leftover build folders cluttering your project.
• Works consistently across Windows, macOS, and Linux.

Do I Need to Do Anything?

If you're using Codeplain's default test scripts: ✅ No action needed - they're already updated!

If you've created custom test scripts based on our templates: 📝 Yes, please update them using our migration guide.

The updates are straightforward:

For Bash Scripts (.sh):

• Move build folders to /tmp
• Add automatic cleanup
• Update path references

For PowerShell Scripts (.ps1):

• Move build folders to system temp directory
• Resolve paths to absolute before directory changes
• Add cleanup in finally blocks

Example Update

Before:

PYTHON_BUILD_SUBFOLDER=python_$1

After:

PYTHON_BUILD_SUBFOLDER="/tmp/python_$(basename "$1")"
trap 'rm -rf "$PYTHON_BUILD_SUBFOLDER"' EXIT

These are some example diffs that you can use to update your custom test scripts:
conformance_tests.ps1.patch
conformance_tests.sh.patch
unittests.ps1.patch
unittests.sh.patch

[NejcS]

It's also important to know how a client's render would fail in case they upgraded the codeplain tool but didn't update their test scripts.

It gets stuck fixing the tests and the tests log files will usually report that the path for the build subfolders is incorrect like:

ImportError: Start directory is not importable
/Users/nejcstebe/codeplain/codeplain/examples/example_hello_world_python//Users/nejcstebe/codeplain/codeplain/examples/example_hello_world_python/conformance_tests/hello_world_python/display_hello_world

[pedjaradenkovic]

I prepared changes for Incode's repo (we can take a look at them tomorrow together) and left a couple of small comments. Rebase, we can test it and check Incode's changes tomorrow and merge!

[pedjaradenkovic]

This line is not needed anymore.

[NejcS]

How come?

[pedjaradenkovic]

Because you have an eraly return on line 464 https://github.com/Codeplain-ai/codeplain/pull/168/changes#diff-053d4fc90f367f8473ae9173df2ffa4c14be1c87e7906ff24447896959c08928R464

[NejcS]

Ah of course. Thanks.

Now I improved this a little but so that it still handles the case where --status or --version are used with --dry-run or --full-plain.