Add ChilliCream Duration scalar and deprecate TimeSpan - #68
Conversation
|
Instead, you can keep |
|
I can do that ... although TBH there is an extremely small chance that someone actually referenced this specification. |
I agree but I'd rather not create a precedent. We have to get used that those specifications are immutable. Let's invest in better tooling to deprecate/redirect older versions. |
|
I added:
Not sure exactly how you want to do it? |
This looks good to me! Maybe put it in bold? Later on, we might want some machine readable format to hide the deprecated specifications from the index (or merge with https://github.com/graphql/gaps/). But this is longer term. Your current sentence looks good to me 👍 |
You can play around with it if you like ... making the whole sentence bold sort of conflicts with the License and Copyright text below it, unless you meant just making the word Deprecated bold? |
|
I have no clue sorry 😅 I just wanted to make sure people didn't miss it. But I'm fine with leaving it as is. |
|
Can this be merged now? 🙂 |
|
Yep, let's merge. I'll also remove that 2 weeks review period, which hasn't been super helpful and just adds friction. Edit: #70 |
Durationbetter matches the underlying spec.TimeSpanwas .NET-oriented.