Replies: 4 comments 1 reply
-
@damyanpetev @zdrawku @pmoleri Guys, we should output the generated code with the licensed version of the packages, instead of the trial ones, when a licensed users is initiating the code generation. |
Beta Was this translation helpful? Give feedback.
-
I was going to mention upgrading the package should be a simple single command affair but then I read this bit:
So assuming you made the licensing changes already and a new generation comes with the entire project overriding them, I can see how that can be a hassle. Are you perchance publishing to GitHub repo? Because the overriding behavior is on our radar and we might have some ideas for GitHub PRs that'll possibly help alleviate this as well. |
Beta Was this translation helpful? Give feedback.
-
@OrigamiPT we have some ideas on how to tacke this problem. The work item is part of our next sprint iteration. I will update the disucssion when we are ready with the implementation. |
Beta Was this translation helpful? Give feedback.
-
@OrigamiPT with today's release of App Builder you will get a licensed code upon export for licensed accounts and code with watermark for trial users.
Thank you for making AB better! |
Beta Was this translation helpful? Give feedback.
-
Hello,
i have an ideia to share with you all, i just purchased a plan for the igniteUI and i saw that when i pull the generated code from indigo that the licensing is not applied and with that each time someone pulls the code from there it has to apply all the licensing stuff to the code, even if i create just a new area i have to change all the code to reflect the licensing.
So the ideia would be for the code generator to check if a license is in place and apply it to the code.
Best regard.
Beta Was this translation helpful? Give feedback.
All reactions