docs(archive,assert,cache,cli,encoding,html,http,net,streams,text): remove unstable Markdown alert

[iuioiua]

No description provided.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.21%. Comparing base (afb9a4f) to head (369f302).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5672      +/-   ##
==========================================
- Coverage   96.22%   96.21%   -0.01%     
==========================================
  Files         481      481              
  Lines       38751    38751              
  Branches     5618     5618              
==========================================
- Hits        37289    37286       -3     
- Misses       1420     1423       +3     
  Partials       42       42              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kt3k]

This text isn't needed. @experimental suffices.

This doesn't seem aligned with CLI's policy.

[kt3k]

I agree with removing the [!WARNING] format for readability in IDE

[iuioiua]

It's true that that the CLI uses the unstable note. But I still think it's not needed. Hints in the IDE show the @experimental tag, and JSR shows an unstable button (example). This unstable notice doesn't seem to provide any added value.

[iuioiua]

Furthermore, while the CLI employs this convention, it's not in the Deno Style Guide. I think these reasons provide sufficient justification to deviate.

[kt3k]

But I still think it's not needed. Hints in the IDE show the @experimental tag, and JSR shows an unstable button (example).

I disagree with this. JSR rendering of @experimental tag is fine, but @experimental tag in IDE is not visible enough.

The Spinner docs in IDE after this change.

It's at the last line, and it doesn't seem enough alerting. It's likely the users miss this.

[iuioiua]

That's because @experimental is the last tag. We should make @experimental always come after the initial description.

We can do:

/**
 * <description>
 *
 * @experimental **UNSTABLE**: New API, yet to be vetted.
 */

WDYT?

[kt3k]

That looks better to me, but I think it's still important for CLI and STD to have the same policy (formatting) for this to make things less confusing.

@bartlomieju What do you think about the above suggested formatting?

[kt3k]

/**
 * <description>
 *
 * @experimental **UNSTABLE**: New API, yet to be vetted.
 */

This now looks a good compromise between consistency with CLI and better rendering in IDE and JSR. Let's do this

[kt3k]

LGTM