:\Īlso good feedback about putting in a warning around the codepoints. But I also understand if it makes no sense to rebuild all or a part of your web project. That would certainly mean that you're using the same codepoints and font. (And btw, it's a very clever idea! And I'm sorry that we aren't going to be able to support it.) There could be an opportunity for you to use Flutter for Web to solve this problem. Since we have always used our own icon font that is updated independently of the public icon font, we never intended (and I certainly never imagined) that people would use the codepoints in projects of a completely different stack. So documentation from that repo is useful for a comparison but doesn't completely apply to what we do in our repo. And like I said, we don't even use this font. The documentation for the icon font that says to use codepoints if required is the HTML guidance, not Flutter. This class is public because people use IconData with their own fonts for custom icons which are then treeshaken. Its api has to use codepoints to correctly access the font. The IconData class is the class backing Icons. , any objection to us removing the line under the description of each Icons? ( IconData(58712, fontFamily: 'MaterialIcons')) That's a good point on the listing of the numbers in the documentation. I'm going to close this issue as 'working as intended' but do write back if there's anything you find that is not working as intended! They are intended to be accessed via the consts that don't change ( Icons class). We also do not recommend using the codepoints directly in Flutter. We have our own release schedule which is independent of the Google Fonts team and we have a version of the icons font that is made especially for us. Unfortunately we cannot guarantee that the font we use will ever match the one in that directory. I'm so sorry that it ended up being trouble for you. And since anyone who updated would automatically have the new mapping, it was not considered a breaking change since it did not break the supported developer experience. The Icons class in Flutter is intended to be accessed via the consts and not via the values they map to. The Google Fonts team asked us if we were ok with that and we said yes. For various reasons I'm not privy to (mostly I believe around a rebuild of their icon->font pipeline) the codepoints in our new change were not going to match older versions of the codepoints. It is not the one you find at google/material-design-icons. The icon font that Flutter uses is not the icon font that's publicly available but rather one that is created especially for Flutter by the Google Fonts team led by When we pull it, it contains the latest of all externally licensed icons in all styles except 2-tone which is not supported in Flutter. I'm sorry it's caused trouble for your project. Hi, ! My name's Will from Material Engineering and I was responsible for this change.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |