Add sv::features attribute to avoid breaking API
#446
Comments
This was referenced Oct 15, 2024
Closed
jawoznia
added a commit
that referenced
this issue
Oct 15, 2024
Remove `sv_replies` feature as it does not make the change non breaking.
jawoznia
added a commit
that referenced
this issue
Oct 15, 2024
Remove `sv_replies` feature as it does not make the change non breaking.
jawoznia
added a commit
that referenced
this issue
Oct 16, 2024
Remove `sv_replies` feature as it does not make the change non breaking.
jawoznia
added a commit
that referenced
this issue
Nov 20, 2024
Remove `sv_replies` feature as it does not make the change non breaking.
This was referenced Nov 20, 2024
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To overwrite Sylvia behavior without breaking the API in minor releases we will introduce new attribute
#[sv::features()].User will be able to pass the currently supported feature to enable new behavior.
For the
replyfeature we will support the#[sv::features(replies)].We will be potentially able to reuse this attribute in the future while implementing better support for
migrate.The text was updated successfully, but these errors were encountered: