Git Product home page Git Product logo

Comments (9)

mislav avatar mislav commented on June 8, 2024 1

@eliperkins That would make it immediately obvious as to which Unicode version is supported by which version of gemoji, but for other purposes I think it will be detrimental since the new versioning policy would clash with semver practices.

For example:

  • gemoji 15.1.0 supports Unicode 15.1. When we fix some bugs with gemoji, we can release that as gemoji 15.1.1, but what if we add some Ruby features unrelated to Unicode? We'd have to tag the next release gemoji 15.2.1, which is a misnomer because Unicode 15.2 does not (currently) exist.
  • gemoji 15.1.0 supports Unicode 15.1. Let's say we update gemoji Unicode support to Unicode 16. This is a backwards-compatible change, since all previous emoji are still supported and apps should be safe to upgrade to this new gemoji version, but we still have to tag it gemoji 16.0.0 (major release = a breaking change in semver) to match the Unicode version.

from gemoji.

xnousnow avatar xnousnow commented on June 8, 2024 1

Any updates?

from gemoji.

Olzie-12 avatar Olzie-12 commented on June 8, 2024 1

^^

from gemoji.

undefinedpersonn avatar undefinedpersonn commented on June 8, 2024

What its up for.When you say the plan,what do you mean?

from gemoji.

sabrican3532 avatar sabrican3532 commented on June 8, 2024

What its up for.When you say the plan,what do you mean?
s***@*******

from gemoji.

sabrican3532 avatar sabrican3532 commented on June 8, 2024

Facebook code

from gemoji.

Jnuhaque avatar Jnuhaque commented on June 8, 2024

Community help

from gemoji.

mislav avatar mislav commented on June 8, 2024

@li910802 Thanks for the suggestion. After Unicode 15 emoji are more widely supported on devices, we will be open to importing the Unicode 15 set into this library. #244 (comment)

from gemoji.

eliperkins avatar eliperkins commented on June 8, 2024

Somewhat related to this discussion, I wonder if making the versions of gemoji match the Unicode emoji versions would be a net-positive for consumers and make it more explicit that it will be a "breaking change" (e.g., you'll need to support new emoji images) when going from one version to the next.

For example, if I only have the emoji images for Unicode emoji 14.0, I'd use gemoji "~>14.0.0". Upgrading to gemoji "~>15.0.0" would be an explicitly opted-into upgrade.

If my app only supports deployment targets where I know Unicode emoji 15.0 exists, I won't be blocked by gemoji updating as well.

I'd love some feedback on this idea!

from gemoji.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.