fac26a6ca0
This commit introduces type validation for parameter values within the parser/compiler, aligning with the YAML schema. It aims to eliminate dependencies on side effects in the collection files. This update changes the treatment of data types in the Windows collection, moving away from unintended type casting by the compiler. Previously, numeric and boolean values were used even though only string types were supported. This behavior was unstable and untested, and has now been adjusted to use strings exclusively. Changes ensure that parameter values are correctly validated as strings, enhancing stability and maintainability.
32 lines
1.0 KiB
TypeScript
32 lines
1.0 KiB
TypeScript
import { RegexParser, type PrimitiveExpression } from '../Parser/Regex/RegexParser';
|
|
import { ExpressionRegexBuilder } from '../Parser/Regex/ExpressionRegexBuilder';
|
|
|
|
export class ParameterSubstitutionParser extends RegexParser {
|
|
protected readonly regex = new ExpressionRegexBuilder()
|
|
.expectExpressionStart()
|
|
.expectCharacters('$')
|
|
.captureUntilWhitespaceOrPipe() // First capture: Parameter name
|
|
.expectOptionalWhitespaces()
|
|
.captureOptionalPipeline() // Second capture: Pipeline
|
|
.expectExpressionEnd()
|
|
.buildRegExp();
|
|
|
|
protected buildExpression(match: RegExpMatchArray): PrimitiveExpression {
|
|
const parameterName = match[1];
|
|
const pipeline = match[2];
|
|
return {
|
|
parameters: [{
|
|
name: parameterName,
|
|
isOptional: false,
|
|
}],
|
|
evaluator: (context) => {
|
|
const { argumentValue } = context.args.getArgument(parameterName);
|
|
if (!pipeline) {
|
|
return argumentValue;
|
|
}
|
|
return context.pipelineCompiler.compile(argumentValue, pipeline);
|
|
},
|
|
};
|
|
}
|
|
}
|