From 95cf4d9310a7b4d7efa2de5583f9d5ddc42b16fa Mon Sep 17 00:00:00 2001 From: Joel Dudley Date: Tue, 27 Nov 2018 17:25:23 +0000 Subject: [PATCH] Remove incorrect info that enums could not be evolved. (#4304) --- docs/source/upgrading-cordapps.rst | 7 ------- 1 file changed, 7 deletions(-) diff --git a/docs/source/upgrading-cordapps.rst b/docs/source/upgrading-cordapps.rst index ff87949cfd..4f36146df6 100644 --- a/docs/source/upgrading-cordapps.rst +++ b/docs/source/upgrading-cordapps.rst @@ -633,10 +633,3 @@ Although not strictly related to versioning, AMQP serialisation dictates that we wildcard * Any superclass must adhere to the same rules, but can be abstract * Object graph cycles are not supported, so an object cannot refer to itself, directly or indirectly - -Writing enums -~~~~~~~~~~~~~ -Elements cannot be added to enums in a new version of the code. Hence, enums are only a good fit for genuinely static -data that will never change (e.g. days of the week). A ``Buy`` or ``Sell`` flag is another. However, something like -``Trade Type`` or ``Currency Code`` will likely change. For those, it is preferable to choose another representation, -such as a string.