🔙 for Backwards compatibility

[shankari]

Emoji symbol

🔙

Emoji code

:back:

Emoji description

Code that adds backwards compatibility

Describe the use case of your emoji

Code that is used for backwards compatibility/live migration of online systems.

• e.g. if the data format was originally {"foo": "bar"} but we want to change it to {"foo1": "bar"} so we write temporary code of the type

if "foo" in object:
    object["foo1"] = "bar"
    del object["foo"]

Is this use case covered by an existing emoji?

No ❌

Does this emoji fall into the "how" or the "what" category?

• [X] This proposal do not describe "how" a commit was made, but does in fact describe "what" is the contents of the commit about.

Examples

https://github.com/e-mission/e-mission-server/commit/3fc3762641642ebcf200c8d83ea6b770c5cb738e https://github.com/e-mission/e-mission-server/commit/1c3f128717c6b8374585eacc9dbf417bda5235b9 https://github.com/e-mission/e-mission-phone/commit/72db83c4c57e9d8f51b0d9a1556a86cf381415aa

Validations

• [X] Follow our Code of Conduct
• [X] Read the Contributing Guide.
• [X] Check that there isn't already an issue requesting the emoji.

[shankari]

I am open to other emoji suggestions; I just think that backwards compatibility is a category of changes that should be captured.

[Thanyanit-J]

How about 🔄 (arrows_counterclockwise) ? The left arrow alone gives the impression quite similar to undo.

When we talk about backward compatibility, we think like:

• old file can run in the new system
• new system supports the old file

So 🔄 seems more clear to me.

[vhoyer]

IMHO, backwards compatibility (bwc) should be included in the original commit that added the new syntax, but I can kinda see why one would want to have this if something was forgotten (but in this case I would use :bug: because if the application needed to have bwc and we didn't add it before, it is a bug to me), or maybe even explicitly separate it to git revert it later...

Anyway, since the back arrow really does remind of the :rewind: emoji, what do you people think of using :t-rex: or :sauropod: (cuz it's a extinct API, get it? funny)

[Thanyanit-J]

Didn’t see the dinosaur coming lol. Those are really good.

“🦖 Ensuring feature backward compatibility“ “🦕 Ensuring feature backward compatibility“

Yeah, looking good 👍

[shankari]

IMHO, backwards compatibility (bwc) should be included in the original commit that added the new syntax, but I can kinda see why one would want to have this if something was forgotten

I prefer to add the backwards compatibility as a separate commit because:

• git commits are supposed to be small and self-contained
• I can revert the backwards compatibility commit later (once we don't have old-format data any more)

Having said that, the dinosaur idea 🦕 (:sauropod:) sounds great!

[Chasmical]

I myself used 🧩 for this purpose, although it's more of a "general" compatibility, rather than backwards- specifically.

[carloscuesta]

I like the idea!

🦖 is just perfect for this proposal