You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello Resilient devs! We are currently using Resilient where I work, and I've been developping a lot of customizations lately.
Because we versionize our customizations, we had to do a private fork of resilient-sdk to suit our needs and tweak it a bit. I'd like to submit some of the changes we made internally here so others can benefit from it.
The changes include:
Deterministic exports using codegen --reload: When regenerating customize.py and export.res, the output currently changes the order of the customizations, which is problematic from a VCS standpoint (diffs are very very ugly). The change we made makes it so the data is ordered before the files are generated, resulting in way, way cleaner diffs.
Reloading workflow documentation files: Once generated, the workflow documentation files (wf_my_workflow.md) are not re-generated when doing "codegen --reload" after initial creation. This results in incomplete documentation and it's harder to review changes in a PR that changes an existing workflow. Our changes make it so everytime codegen --reload is executed, the these files get regenerated.
Removing the "id" fields in export.res: The Resilient export exports all fields in the customizations (including the ID field). However, Resilient does not seem to use this field anymore. When two different dev environments are set up, there can be differences in the IDs of the same customizations, resulting in a weird "back-and-forth" phenomenon that makes some pretty ugly diffs in a PR. Our change remove these fields, and everything seems to be still working perfectly fine.
Exporting layouts: Resilient-sdk receives the layouts information in the export, but strips it and doesnt include it in the export.res file. Our change make it so the layouts can be exported the same way fields and workflows can, so we can versionize them.
Please tell me if you are interested in any of these changes, and I'll make PRs!
PS: I really love this product and the way it is architectured. It's very powerful and allows devs to do awesome things with it. Keep up the great work :)
The text was updated successfully, but these errors were encountered:
Hello Resilient devs! We are currently using Resilient where I work, and I've been developping a lot of customizations lately.
Because we versionize our customizations, we had to do a private fork of resilient-sdk to suit our needs and tweak it a bit. I'd like to submit some of the changes we made internally here so others can benefit from it.
The changes include:
Please tell me if you are interested in any of these changes, and I'll make PRs!
PS: I really love this product and the way it is architectured. It's very powerful and allows devs to do awesome things with it. Keep up the great work :)
The text was updated successfully, but these errors were encountered: