Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Moved component locations should be marked as breaking changes #1268
Comments
|
We can't guarantee that locations or APIs of internal component will never change, and we can't treat them as breaking change ether. Feel free to send a pull request to the docs to clarify that. |
|
Maybe we should maintain a public API mapping where we expose components? Extensibility is one of the great aspects of styleguidist and I think it's a valid point that such changes should not break existing usages. |
|
This sounds great in theory but in practice I don't see it practical. And like with any “we should do”, someone will actually have to do this work. |
When upgrading to the beta I got this error:
When I change the path to
react-styleguidist/lib/client/rgs-components...it compiled.Since these module locations have been treated as public API (for overrides), their change in location should be documented as a breaking change.