Open dingram opened 7 years ago
sounds good, but not possible or viable.
Example 1: in leaflet & leaflet.draw the value of the earth radius was changed to reflect the simpler values used by Nia.
Example 2: in most css files image references where replaced by the @@IMAGE@@ build makro. okay. This could be easily be moved into an extra css but would again break on a library update.
IMHO its better to make clear that these files were modified.
A simple file-rename could warn developers ("leaflet-src.js" -> "leaflet-src-mod.js")
Additional as developer rule: always commit the unmodified version first then commit modifications. This way you have a nice git log what and why was modified.
as an example: PR #1168 it was (nearly) done be simply cherrypick the old modifications.
I just skipped the 'rename the file' part.
@McBen
Various third-party libraries used by IITC have been customized in one way or another. These customizations should either be submitted upstream, pulled out in some way, or monkey-patched (as a last resort).
Having modified third-party code in the main repository makes it very hard to upgrade, and also means that the final JS is much larger than it strictly needs to be.