Adjust Reflective to improve readability or ease-of-use?
See original GitHub issueAs discussed in https://github.com/diffplug/spotless/pull/283#discussion_r211358920, I think we should consider changing the Reflective
class in lib
to mimic JOOR`s API.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Proofreading with Readable - 7 strategies to instantly improve ...
Here are 7 strategies to simplify your writing and improve the readability of what you write: 1. Use short, easy words. The more...
Read more >Readability Assessment of Online Patient Education Material ...
The results of our study are meant to instigate reflection, to initiate efforts by website authors to improve readability, and to serve as...
Read more >The Principles of Readability - ERIC
The first aim of the classic readability studies was to develop practical methods to match reading materials with the abilities of students and ......
Read more >Blazepod Flash Reflex Training System for All Types of Sports
Blazepod flash reflex training system offers an innovative light-based kit for all athletes and coaches to jack up agility, reflex, quickness, and coordination....
Read more >Enhance Readability and Viewing | DURAVUE Coatings
Anti-glare and anti-reflective treatments are used to improve readability of a displayed image or set of characters, but attack the problem using different ......
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 FreeTop 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
Top GitHub Comments
It sounds great! I think it’s important for Spotless to be easy to contribute to, and there are two conflicting forces here:
The compromise we’ve struck so far is that the core is strict, well-organized, and relatively hard to contribute to. But adding a new step has been loose, and we’ve merged anything useful with unit tests to make sure it stays working. I think that’s a good compromise that I’d like to keep working. I think refactoring to jOOR-ish will help organize the project, and make it easier to contribute. But I do want to stay loose with accepting new formatters so long as they keep their messiness internal.
Coming up on a year of inactivity. I’m happy to accept PR’s in this direction, but I don’t think it’s a priority. Happy to reopen when/if someone has time to move this forward.