I think I’ve found the cause of the error. I’ll hop on that asap.
If anyone else is also having similar issues with the API dump in any separate projects, it appears the current version endpoint (versionQTStudio) is returning an outdated version.
Using the DeployHistory endpoint will give you the latest.
Has there been a fix for Path2D waypoints? I recently tried to use Codify to generate a code for Path2D instances, however it just gives me a blank one.
I’ll have a look into this one. It’s because Codify just serialises the hierarchy, and I’m sure waypoints need to be retrieved programmatically? Either way, I’ll investigate. Thanks for the report.
No problem, I think you just need to use the :GetControlPoints() method on the Path2D instance, then set the newly created Path2D’s control points with the :SetControlPoints() method with the given array.
Updated API URLs to (hopefully 
) prevent errors when attempting to Codify newer Instances (e.g. Path2D, UIFlex, DragDetector, UIDragDetector, etc.).
Added option for Color3 hex codes to be formatted in lowercase. You can configure this from the Color3 formatting settings.
Added support for Path2D waypoints* when using the Regular framework (no framework). Due to the Path2DControlPoint datatype and how waypoints are assigned to Path2D instances, they cannot be assigned when using a framework.
*Path2D waypoints are not currently supported in the demo version of Codify.
Is there a way to purchase this plugin with robux?
very useful plugin, has saved me hours of time during development.
Fusion is now at v0.3, may you update the plugin to use this version? The snippets don’t work directly anymore because New is not assigned. They’re in scopes instead.
Also, with the release of Instance:IsPropertyModified(), I believe it’s possible to shorten the generated property assignments. It should not assign the property if it is not modified! That will remove the unused propertys like BorderSizePixel that keep showing up in every GuiObject’s code…
I can’t enforce this currently, as people may still be using a version lower than 0.3. You can manually change the settings, however, I will probably set scopes as the default from Codify v3 onwards (which will allow for some breaking changes).
Codify has never applied properties when they’re unchanged from their default value. I think what you’re referring to is the “default” values Studio applies (for convenience) when you create them using the Insert Object menu vs. Instance.new.
Codify v2.5.1 introduced a setting that allows background and border-related properties to be omitted when the GuiObject is completely transparent; however.
(fwiw, the property methods are not yet enabled either, but I cannot wait for a full property API, which would mean I could eliminate HTTP requests entirely).
Hey, I wanted to introduce you to my own instance framework:
It would be really cool if your plugin would be able to support it
I don’t plan on adding additional frameworks to the current version (v2.x) of Codify, but I’m determined to expand the capabilities of Codify in v3.x to allow for custom shareable generators.
Does it support vide jsx? I can see that it supports typescript jsx but i wanna make sure i can use it with vide 
I think so? As far as I know the core JSX syntax is identical regardless of whether you use Fusion, React or Vide. I think the only difference is that Fusion JSX also requires a “scope” param, which Codify doesn’t currently support. However, I don’t use TypeScript myself with Roblox, so I can’t confirm if this is correct.
Every time I hit play test, codify reopens, and repeatedly reopens even after closing it. Mildly annoying. I’ve been having this issue for a while, not sure since when. Each time I hit play test or open a place it opens, where I have to then close it until I hit play test again.
I’m aware of the problem and have a fix, but don’t have any internet at home at the moment to publish. Will update when I’m back online.
Are you using the free or paid version?
I’m using the paid version.
the plugin keeps crashing when I run it could you fix this?
