Breaking change with no class in quotations
See original GitHub issueIn previous versions you could set a class to empty for example we had several projects with
initial : "",
so that it wouldn’t add an initial class. With the new changes for multiple classes that throws an error and prevents headroom from running. We had done this as we didn’t want additional classes we didn’t need added to things.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
c# - Is it a breaking change that modifying the access modifier ...
The question is not "is this a breaking change?" It clearly is; almost every change is some kind of breaking change.
Read more >Extended Rules for Using Quotation Marks - Purdue OWL
However, there are approved methods for altering quotes for either clarity or succinctness. Quote length. If the original quote is too long and...
Read more >Am I allowed to make changes to direct quotes in APA style?
Yes. You may want to make minor changes to a direct quotation. This is possible (as long as you don't change the meaning), ......
Read more >Working with Quotations | Writing Support
Yes, you can leave out words you deem unnecessary in a quotation, but you can't take out words that will change its meaning....
Read more >Integrating Quotations | Advanced Rules | MLA Style
In a block quotation, almost all the regular rules for quoting are inverted or changed. There are no quotation marks, the entire quotation...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I was going to ping you to ask your opinion @hacknug, since I saw you had commented on a previous issue. Interesting that you’ve changed your mind since.
I’m not averse to this idea in principle, but as I said it would require a fairly substantial rewrite of the internals. I plan to do this eventually, but not right now. I will come back to this then
As one of the people who brought this up a couple years ago, today I wouldn’t bother adding support for it. Like @WickyNilliams said in https://github.com/WickyNilliams/headroom.js/issues/226#issuecomment-223307160, without any real performance issues, I don’t think it’s worth the effort.
If you wanna take a stab at it and open a PR, I’ll try to review and test the changes but again, please make sure it makes sense to spend time and resources into this.
I agree with you but you need to keep in mind you should only remove useless stuff. The classes we’re talking about are used to keep track of the instance’s state (unlike WordPress which in my cases are useless 99% of the time).
The creator of the library literally told you it would require to rewrite the whole state-management part of the library. Make sure you keep this in mind if you end up trying to change the way the library works 👍