-
Notifications
You must be signed in to change notification settings - Fork 206
Standardize specifications #105
Comments
cc @anubhav7495 as he's been helping out with extensive reviews recently. Some of the discrepancies that I've observed in PRs we've received that would be useful to document better for the specification:
|
+1 to all of these The data caching step isn't currently supported by a few implementations, so we could either:
This sets a precedent for future additions to the specifications. |
👍 from my side too. Also, some older apps list 20 stories per page instead of 30. We should also open PRs for those implementations. Examples: |
How do y'all feel about standardising the data fetching, CSS, routing(?) etc so that the examples are more purely focused on the UI implementation side of things? Similar to todomvc-common. |
what about sites hosted on different platforms that will result in different response times? will be ideal to have a single host provider to avoid any response discrepancy between the different providers |
also all demos should be single page website, some demos are some aren't, but adding this behavior can add some extra kb to the request, having a direct impact on the speed. ps: would be nice to add as a metric the js size on the initial page load. |
Some discussion has been made to standardize specifications between the different implementations - let's use this ticket to discuss how we can/should do this.
The text was updated successfully, but these errors were encountered: