Can someone explain what they mean by “tacked-on”?
It’s bad DX but if you provide an invalid ID it should return the valid ones
Pretty sure the OpenAPI docs include the model IDs too
@georgecollier Where does this come from? Some kind of built-in Bubble app version numbering? Never heard of it.
In Comments:
In Tests:
Probably somewhere in your app source code even if it’s been deleted
@georgecollier Any vision on adding some sort of documentation feature to Buildprint to autodocument apps for user facing docs? Asking because I was going to start building this for my app, but will wait if it’s coming soon from your end.
Have you tried asking BP for that?
At least for specific modules and flows, it documents very well, with flowcharts and everything.
Regarding the model and structure, you can provide or detail it as you wish. But don’t trust the output 100%, sometimes it gets things mixed up (at least that was the case a few weeks ago).
Maybe you can create your own skill for that.
Windows support has just been added
Hey @pbenito if you don’t mind me asking: you’ve been off this forum for a while – are you back on because of Buildprint?
I used to visit quite often, but usually I don’t post threads on it. Buildprint has been an incredible asset to Bubble environment, but no, I’m not back because of it hahaha
Yup, I have, but I do need to get it into a knowledge base that’s user facing on the support center. I rather have this automated where it fetches from Buildprint’s agent and then another agent on my lambda takes control and updates the docs, a middleware.
Yup, I do this for internal docs, but for user facing, I need to get it onto my knowledge base so planning on building a middleware using the CLI that grabs information and diffs and updates the docs with its own summarization model!
Be careful to not expose to the user things they shouldn’t know, especially if you’re going to allow interaction.
@georgecollier Known issue or is this just me?
Happens only when reporting this specific issue. Started a new conversation and no longer seeing the error. But the format as JSON issue I pointed out should be added to skillset 
Was the number being referenced by any chance in a backend workflow / custom event parameter?
Yeah, will def. setup some guardrails.
What specifically did it try to put :formatted as JSON safe on there?
cool fix out tomorrow
It’s specifically for ‘This X’ inside :format as text, schedule API workflow on list, make changes to list of things etc