Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates TLC custom option variable substitution so ${specName} / ${modelName} resolve to the base filename without any extension (fixing cases like embedded CONFIG in a .tla producing HourClock.tla.dot).
Changes:
- Replace
path.basename(file, '.ext')withpath.parse(file).namefor${specName}/${modelName}expansion. - Ensures correct output filenames regardless of whether the model/config source is
.cfgor embedded in.tla.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
When using ${modelName} or ${specName} in TLC custom options, the
variables now correctly resolve to the base filename without extension,
regardless of whether the file has a .cfg or .tla extension.
Previously, path.basename(file, '.ext') would only strip the specified
extension, causing ${modelName}.dot to expand to "Model.tla.dot" when
the config was embedded in a .tla file instead of the expected
"Model.dot".
Now using path.parse(file).name which properly strips any extension.
Fixes Github issue #483
#483
[Bug]
Signed-off-by: Markus Alexander Kuppe <github.com@lemmster.de>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When using ${modelName} or ${specName} in TLC custom options, the variables now correctly resolve to the base filename without extension, regardless of whether the file has a .cfg or .tla extension.
Previously, path.basename(file, '.ext') would only strip the specified extension, causing ${modelName}.dot to expand to "Model.tla.dot" when the config was embedded in a .tla file instead of the expected "Model.dot".
Now using path.parse(file).name which properly strips any extension.
Fixes Github issue #483
#483