fix(fields): add job not found messaging to AS_TOOK
#141
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.
I was experiencing issues in my workflow where
process.env.AS_TOOK
was coming through asundefined
. This was not a matrix build or anything special, and I was only specifying this field to be added alongside a custom payload.Turns out I had not specified the
job_name
since I had customized it in the workflow. I only found this out after looking through the code and realizing there's a nice helpful debug message pointing to the documentation 馃槃Although, as it turns out, this debug message was being assigned to the wrong
process.env
variable. I was only usingtook
and it was getting written toprocess.env.AS_JOB
.Since the same message is already attached to the correct env variable in
this.job()
, I've simply changed.took()
to useAS_TOOK
. Now, you'll see the same helpful debug message rather than justundefined
if you haven't configured things quite right in the workflow.