Repository navigation
Name .NET and Node.js among the languages on the new usage sharing defaults - #324
Draft
jwrosewell wants to merge 1 commit into
Draft
jwrosewell wants to merge 1 commit into
jwrosewell wants to merge 1 commit into
Conversation
Contributor
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
documentation#323 added a sentence to the usage sharing page and to the Evidence key filter page, naming the languages that follow the new usage sharing defaults (Go and Rust) and those still on the old ones (.NET, Java, Node.js and Python). Since then 51degrees-dotnet#244 merged into the .NET
rcat 04:01 UTC and 51degrees-node#135 into the Node.jsrcat 04:02 UTC on 15 November. Once those releases reachmain, both sentences put .NET and Node.js on the wrong side.What the specification says
usage-sharing-element.md lines 65 to 69 at b3b2c0dd, the head of the specification's
rc, which holds specifications#155:Lines 80 and 81:
What changed
src/pipelineapi/features/usagesharing.mdline 90 now says .NET, Go, Node.js and Rust follow these rules, and that in Java and Python sharing all query string parameters is still off by default and sharing all Evidence also shares every cookie.src/pipelineapi/concepts/data/evidencekeyfilter.mdline 52 says the same of the Evidence key filter.Nothing else on either page changes.
Each language on its
rcat 04:30 UTC on 15 November51D_ones with all Evidence sharedConstants.csline 106 andEvidenceKeyFilterShareUsage.cslines 304 to 312 at f18eb7b5, from #244shareUsage.jsline 154 andshareUsageEvidenceKeyFilter.jslines 76 and 121 to 126 at 0e89a400, from #135ShareUsageBuilderBase.javaline 68 declaresshareAllQueryStringParameterswith no starting value, so it is false, andEvidenceKeyFilterShareUsage.javalines 200 to 202 share every key when all Evidence is shared, before the cookie rule, at 2eebbff3. 51degrees-java#160 makes the change and is an open draft.share_usage.pylines 106 and 111 defaultquery_whitelistto an empty list andshare_allto false, andshare_usage_evidencekeyfilter.pylines 100 and 101 share every key not in the never shared list when all Evidence is shared, before the cookie rule, at 0cc7aa14. No pull request makes the change yet.When this merges
Into
rconce reviewed, and intomainwith the documentation's release after the Monday language releases reachmain, as documentation#321 and #323 do. If 51degrees-java#160 or a Python change merges into itsrcbefore then, this draft names that language too before it merges. If .NET or Node.js misses the Monday release, this draft goes back to naming it.Build
To follow once the checks on the head finish.