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

object: Purge notification attributes #287

Merged
merged 1 commit into from
Feb 27, 2024
Merged

Conversation

cthulhu-rider
Copy link
Contributor

No description provided.

Copy link
Member

@roman-khimov roman-khimov left a comment

Choose a reason for hiding this comment

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

Can we deprecate them without deletion?

@cthulhu-rider
Copy link
Contributor Author

@roman-khimov deprecate means keep supporting, while lookin at #279 i thought we wanna stop supporting. CMIIW

@roman-khimov
Copy link
Member

There is a difference of API-level and node-level for us. I want to drop this from node, obviously, but API-wise we can still remember these were used (and not add any additional meanings to them, for example).

Notification attributes turned out to be unusable. Nobody uses them, so
they are deprecated.

Closes #279.

Signed-off-by: Leonard Lyubich <leonard@morphbits.io>
@cthulhu-rider
Copy link
Contributor Author

got it, done

@roman-khimov roman-khimov merged commit 24b5c5d into master Feb 27, 2024
3 checks passed
@roman-khimov roman-khimov deleted the 279-object-drop-ticks branch February 27, 2024 06:31
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