You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add support for setting sitemap options directly in route options (RouteCollectionProvider)
Add a caching layer for providers with expensive calculations
Add a ChangeFrequency class/interface with common change constants
Introduce streaming somehow to improve memory efficiency
These are the things I have in my mind so far.
I marked BC breaking changes with italic. In these cases TODOs and deprecation warnings should be triggered.
Ultimately I think this project could also have it's own organization. Like sitemaphp (which I immediately registered, just in case :D, can invite you if interested)
There are many others as well, but I found yours to have the most decent API and workflow (actually I started to develop exactly the same)
The text was updated successfully, but these errors were encountered:
I referenced the improvements you listed here in a new issue that will contain the things I want to see in a new version. I also have created separated issues for some of the items listed here.
Apart from the changes I suggested in the previous issue, I have a few ideas to improve package quality:
setImages
,setVideos
)Interface
suffix: Symfony, Zend and the FIG still pushes it, but fortunately more and more developers realize, it's evil (reference: http://verraes.net/2013/09/sensible-interfaces/)AbstractProvider
into smaller components: extract route generation logicBaseFormatter
ChangeFrequency
class/interface with common change constantsThese are the things I have in my mind so far.
I marked BC breaking changes with italic. In these cases TODOs and deprecation warnings should be triggered.
Ultimately I think this project could also have it's own organization. Like sitemaphp (which I immediately registered, just in case :D, can invite you if interested)
There are many others as well, but I found yours to have the most decent API and workflow (actually I started to develop exactly the same)
The text was updated successfully, but these errors were encountered: