Nathan,
I do not see anywhere relevant to where you initialize response. you that a setter for response that relies on response already being set, so this code, imo, is not the problem.
Les
Out on HF and heard nobody, but didn't call CQ? Nobody heard you either. 73 de N7GH
I don't think anything "goes to null". What I think is that "this" refers to different things at different places in that code, and you're assuming that it's always the same.
I've tried this several different ways. I even put an input as a typescript variable and pass it in the loop, but it always becomes null when I try to use it. It doesn't do this in Java. There is something wrong with the way this language works I think.
I had to do an ngModel for the varaibles itemName and itemDescription, put them into local Storage, retrieve them in the onSubmit() method so they wouldn't be null, and now it works.
straws are for suckers. tiny ads are for attractive people.
SKIP - a book about connecting industrious people with elderly land owners