Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

*: drop subnet support #420

Merged
merged 1 commit into from
May 24, 2023
Merged

*: drop subnet support #420

merged 1 commit into from
May 24, 2023

Conversation

roman-khimov
Copy link
Member

We don't need them and while there are reasons to have some remnants in the protocol itself we can remove them from the SDK immediately to not include them into the 1.0.0 release.

Refs. nspcc-dev/neofs-api#261.

We don't need them and while there are reason to have some remnants in the
protocol itself we can remove them from the SDK immediately to not include
them into the 1.0.0 release.

Refs. nspcc-dev/neofs-api#261.

Signed-off-by: Roman Khimov <roman@nspcc.ru>
Copy link
Contributor

@notimetoname notimetoname left a comment

Choose a reason for hiding this comment

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

Will we drop in the test scenarios too?

@roman-khimov
Copy link
Member Author

I've seen that, but there is still this field in JSONs and I'd keep them in tests (just to ensure compatibility) until we drop it from api-go.

@cthulhu-rider cthulhu-rider merged commit 5f07bcf into master May 24, 2023
@cthulhu-rider cthulhu-rider deleted the drop-subnet branch May 24, 2023 14:47
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.

4 participants