Skip to content

Conversation

damirka
Copy link
Contributor

@damirka damirka commented Aug 28, 2024

Description

We're deprecating this module for now.

Test plan

Not much to test.


Release notes

Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.

For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

  • Protocol:
  • Nodes (Validators and Full nodes):
  • Indexer:
  • JSON-RPC:
  • GraphQL:
  • CLI:
  • Rust SDK:
  • REST API:

@damirka damirka self-assigned this Aug 28, 2024
Copy link

vercel bot commented Aug 28, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
sui-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 12, 2024 9:13am
3 Skipped Deployments
Name Status Preview Comments Updated (UTC)
multisig-toolkit ⬜️ Ignored (Inspect) Visit Preview Sep 12, 2024 9:13am
sui-kiosk ⬜️ Ignored (Inspect) Visit Preview Sep 12, 2024 9:13am
sui-typescript-docs ⬜️ Ignored (Inspect) Visit Preview Sep 12, 2024 9:13am

// Copyright (c) Mysten Labs, Inc.
// SPDX-License-Identifier: Apache-2.0

#[allow(deprecated_usage)]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A bit ridiculous, but every function in the sui::url uses the deprecated Url type. 😆

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tzakian, I wonder if we should just suppress deprecation usage within the same package... Or maybe somehow with public functions? Not sure.
My point is that these warnings here are not-actionable. We cannot break the API

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmm I'm of two minds on it.

One one hand warning about deprecations on APIs that you cannot change is quite annoying. On the other hand, this might be the only way folks find out about the deprecation, and that they may want to add new functions that use the new type (etc).

I kinda would lean towards the second opinion the most here (we should warn, and folks need to manually turn it off).

@damirka
Copy link
Contributor Author

damirka commented Sep 12, 2024

@tnowacki so deprecation of type makes more sense. The case that I was most worried is creating new coins. By deprecating the type and allowing url::* functions we don't emit deprecation warning in coin::create_currency and its derivatives.

It's good to go in my opinion.

@damirka
Copy link
Contributor Author

damirka commented Sep 24, 2024

@tnowacki @tzakian what are we going to do with this? Thoughts? Opinions? Suggestions?

@damirka
Copy link
Contributor Author

damirka commented Feb 3, 2025

Closing this PR, replacing with a task to handle sometime this year.

@damirka damirka closed this Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants