You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is not uncommon for program developers to sunset their instructions by first, logging a deprecation warning and then removing it completely by throwing an error when the archived instruction is recognised by the program.
It would be nice for Codama to keep track of that information via a status attribute or even a dedicated InstructionStatusNode. The instruction status could be things like:
live if the instruction is accessible (the default state).
deprecated if the instruction is about to be archived.
archived if the instruction is no longer accessible. Note that this is better than simply removing the instruction from the Codama IDL as explorers would still need to parse old instruction for the program.
We could even imagine more advanced statuses like:
draft if the instruction is accessible but not fully implemented yet.
unaudited if the instruction is accessible and fully implemented but no audit was performed for it yet.
Additionally, an optional statusMessage attribute could be useful for program maintainers to provide more information about the current status to their consumers.
The text was updated successfully, but these errors were encountered:
It is not uncommon for program developers to sunset their instructions by first, logging a deprecation warning and then removing it completely by throwing an error when the archived instruction is recognised by the program.
It would be nice for Codama to keep track of that information via a status attribute or even a dedicated
InstructionStatusNode
. The instruction status could be things like:live
if the instruction is accessible (the default state).deprecated
if the instruction is about to be archived.archived
if the instruction is no longer accessible. Note that this is better than simply removing the instruction from the Codama IDL as explorers would still need to parse old instruction for the program.We could even imagine more advanced statuses like:
draft
if the instruction is accessible but not fully implemented yet.unaudited
if the instruction is accessible and fully implemented but no audit was performed for it yet.Additionally, an optional
statusMessage
attribute could be useful for program maintainers to provide more information about the current status to their consumers.The text was updated successfully, but these errors were encountered: