First Run of now-sdk transform Creates Metadata Instead of Fluent Files

Chris Yang
Tera Sage

Hi everyone,

I’ve noticed something interesting with the "now-sdk transform" command and wanted to share my experience in case it helps others (or maybe gets some attention from the team 😊).

On the first run of "now-sdk transform", it generates everything as metadata files rather than placing the output in the "src/fluent/generated" folder. That means the generated files aren’t editable through the Fluent framework — and we all know editing raw XML files isn’t the recommended (or fun) way to go.

 

However, if I delete the "metadata/update" folder and run "now-sdk transform" again, it behaves exactly as expected:

  • Fluent-compatible files are nicely generated in "src/fluent/generated" wherever possible
  • Only the more complex objects remain as XML in the "metadata/update" folder

This lets us start editing properly with Fluent — which is great!

 

Question for the community / maintainers: Is there a reason we need this manual step (deleting the folder) on the first run to get the correct, editable Fluent output? It would be awesome if this could happen automatically from the start.

 

Thanks for any insights! 🙌

0 REPLIES 0