4 ms·
Did you figure out what the greyed out "v1", "v4", etc. after certain calls was for? I clicked through a few pages but couldn't figure it out. Internal version
by mattmanser 6y ago
Did you figure out what the greyed out "v1", "v4", etc. after certain calls was for? I clicked through a few pages but couldn't figure it out.
Internal versioning as they release new methods on their own libraries? So it doesn't break old ones?
- pbiggar 6y agoThat's right, we version all stdlib functions. I talk about it a bit here: https://blog.darklang.com/how-dark-deploys-code-in-50ms/ https://blog.darklang.com/how-dark-deploys-code-in-50ms/ When we add a new version of a function, all the calls to the old function are unchanged. The autocomplete shows new users the new version (and not the old version), while people who are calling the old version get shown both.
- steve_adams_86 6y agoIs this what you refer to as feature flags in the FAQ? > Q: Deployless seems dangerous! Won't I constantly break my application? > A: ... snip ... With Dark's feature flags, you have precise control over how and when a specific feature or set of features becomes live, and for which part of your user base.
- pbiggar 6y agoNo, feature flags are used to wrap an expression and conditionally choose another expression. Its a fancy if expression. In Dark you add one by selecting `add-feature-flag` from the command palette.