I’ve been working on this typesafe UI Library for almost 3 years. All of these components are hoarcekat compatible. To keep the framework lightweight, all components can be created with minimal buy in to the other features offered.
Highlights
Here are just a few of the 29 (as of v9.2.2) different UI components.
Slider
Checkbox
Text Field
Dialog
Circular Progress Indicator
Search Bar
… and 23 more!
Enjoy!
If you have any ideas, or find any bugs, please either post here or make an issue on the github page! Thank you!
Wally support, Fusion+Roact compatibility, hoarcekat stories, open-source GitHub, wide coverage of typed MD3 components and of course this big documentation…
this is an incredible gift!
So hey, let’s do the nitpicks to make it perfect:
Badge: The circle seems clipped and not perfectly round:
Outlined Icon Button: Another circle clipping issue, this one is clearly visible:
FAB: Not really visible, but it feels like there’s a cutoff here as well. The sides seem cut off sharply.
Extended FAB(docs): This link goes to the FAB README, saw you just merged the PR so this is solved!
Assist/Filter Chips & Buttons: Same feedback again, intrusive clipping:
Dialog: Hover effects seem to increase the length of the body.
Well, these are all visual nitpicks. If you can resolve the clipping issue, I suppose this is already production-worthy. The technical side of the library (which you have visibly invested in) looks really good, didn’t expect the whole theme engine to be ported over!
Alright! Version 9.2.2 should have all of these changes. I’ll be going through and updating the documentation preview gifs later today. Thank you again!
So, to my understanding this is what happens when the studio internal language service provider is overwhelmed. If you do ever move to VSCode, you can change the configuration of the LSP plugin flags to have it handle things much more smoothly, however that probably doesn’t help you right now.
Long term it might be worth pursuing a more advanced build / publish workflow to export each workflow compatability separately (for example SyntheticFusion, SyntheticRoact, etc), as well as provide versions which can be downloaded that have the type safety stripped out of them.
Here are some potential workarounds to try in the meantime:
press ctrl+shift+f to open the find all / replace all menu. Then go and replace all --!strict mentions in the package with --!nocheck.
in file -> Studio Settings -> Script Editor, consider lowering the “Large File” thresholds
go through and delete any script named “Fusion”, “Roact”, or “Wrapper”, excluding the workflow you intend to use. Do not delete “ColdFusion” as that’s the source code.
go through and delete all the complex types, aka anything that includes a <...>, {...}, |, &, ? - this will break a lot of the editor type safety, but reduce the burden on the solver without changing any runtime behavior.
Will definitely follow up with you once I have some official solutions. Thank you!
