My pleasure! Welcome back to the InterSystems Development Community!
- Log in to post comments
My pleasure! Welcome back to the InterSystems Development Community!
Looking at https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cl… (thanks DC.AI.!!) if you set a process private global as a flag in OnBeforeAllTests() it will survive any NEW calls in your code, so you should be able to use that to signal that it is part of a unit test.
@henry - thank you for all of your investment in the D.C. as a Moderator!!
can't wait to see the end result! thank you for the relentless work to keep improving the D.C user experience!
yes, yes, YES! I have always been so impressed by this aspect of the ISC stack :)
Got it, thanks for clarifying
SDS has been supported since Caché, what are your version concerns?
For the record, formal best practice across all InterSystems internal applications, as well as InterSystems-led implementations of HealthShare and TrakCare/Intellicare is to use SDS so that Production classes / code can be consistent across all all source code branches.
The CCR Technical Implementation Specialist certification covers topics related to Change Control, Source Control, Environment Management, Standard/Emergency/Normal Changes, etc. So there is additional knowledge you demonstrate from this but it's not the main point of the certification
Done! (finally ... sorry it was so late)
Looking forward to seeing the finished result :)
Happy Anniversary ISC D.C.!
very kind of you to say!
@henry - thank you for all you contribute to our community!!!
thank you for the time you spent writing this. very helpful!!
Welcome to the Developer Community!!
You could gift some points to some well deserving InterSystems interns ... or get socks for everyone on your Christmas list this year ;)
I also had the opportunity to introduce our interns to Global Masters and see them have fun with the gamification challenges :)
Thank you Global Masters team for all of your great contributions to the Community!!
its been a pleasure working with you and learning from you all of these John!!
Thank you for the really clear write-up on this!
@Yuri Marx - thank you for time you spent pulling together this article ... well done :)
@David McCaldon - exciting news, thank you for the work on getting this released!
"all these discussions are mostly useless. " - we have implemented linting as part of server-side source control hooks. See https://openexchange.intersystems.com/package/isc-codetidy
got it - I reached out to the Docs team to better understand why the button isn't there
I completely agree! Doc offers a direct channel to them for feedback, and they are very responsive to that.
Every documentation page has a Feedback button on the right, which will capture the page from which the feedback originates, making it even faster for the Docs team to know where a tweak is needed:.png)
The DC answer is right. You may log in at login.intersystems.com and go to Options > Change Email.
You will need to input a code to verify your new email and a notification gets sent to the old email.
(credit for answer @Pravin Barton )
excellent work!! thank you for the time you took to put this together
congrats to the winners!
glad to hear it!
This is coming from the Source Control class set up in this Namespace. If you search for "Source Control" in the SMP, and look at the settings for that Namespace you will see that a class is selected. Change to None if you don't wish to have Serverside (embedded) Source Control active. If you do wish to use embedded source control, then you will need to provided item type mappings in the ^Sources global in order for it to work (at least to allow the one you currently have active to work - different hooks work differently in terms of configuration)
Great work on this @Evan Gabhart !! Will save a lot of time :)
love it! great work everyone :)
8/12 :)