Variables missing from code generator forms


(Robert) #1

A lot of variables are missing from my code generator forms, e.g. in this one there’s no AppFqn.

In this one there’s no templateId:

If I copy the code and pate it into apiary.io, I get fields in its code generator form. It also shows the code as valid, where Stoplight shows 19 errors.


(Taylor Barnett) #2

Hey @robert, errors or warnings? Warnings shouldn’t be causing it, but it we may need to dig deeper in your specification to see what might be going on.


(Robert) #3

These were working in the 3.8.4 doc and I don’t believe we changed the code.

I guess I could diff the two and see.


(Taylor Barnett) #4

We did some playing around with it and it appears to maybe be something in the UI. We’re actively digging into it now.


(Robert) #5

@taylor any progress?


(Taylor Barnett) #6

Not yet, we’re trying to get the v4.8.0 tested so it can be released in the next few days, so the team has been pretty busy with that and unable to come back to this issue. We’ll get it figured out but it might take a bit.


(Robert) #7

Seems strange that it’s a problem in https://striim.docs.stoplight.io/version390 but not in https://striim384.docs.stoplight.io since there’s not much difference between the two.


(Robert) #8

Any progress on this?


(Taylor Barnett) #9

It is schedule to be (hopefully) fixed in the next engineering sprint, which starts tomorrow.


(Robert) #10

This bug is now affecting striim384.docs.stoplight.io as well.


(Taylor Barnett) #11

Just checked on the ticket internally, it is in the current engineering sprint, but we haven’t worked on it yet. I’ll work on adding the other spec document to the examples of where the bug is happening.

I’ll also try again to replicate it in a smaller example. I don’t think I had any luck last time.


(Robert) #12

Any progress on this?


(Taylor Barnett) #13

@robert just checked and it looks like the team dug into it, but the fix is not as simple as we thought it might be.

They did find one workaround. I know it might not be great and an inaccurate representation of your specification. But if you remove one of the schemes in your specification (http or https), it fixes the problem. You should be able to have both though, but it is triggering the bug.


(Robert) #14

Thanks! Please let me know when I can put back both schemes.


(Robert) #15

Is this still work in progress?


(Taylor Barnett) #16

The web app release did go out today, but we haven’t cut the desktop release (which is why you haven’t seen a changelog yet). This should be fixed in the web app now if you want to try it out.


(Robert) #17

Looks good now! Thanks.


(Taylor Barnett) #18

Yay! Glad to hear it.


(Taylor Barnett) #19