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
There's work being done to modernise the code across MDN: #143.
But there are still complaints such as #146, (partially) about keeping everything synchronised.
One problem with modernising everything, and keeping it in sync, is that examples from examples' repositories are copied inline. This is problematic because updates to either page now require porting the work to the other repository.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
There's work being done to modernise the code across MDN: #143.
But there are still complaints such as #146, (partially) about keeping everything synchronised.
One problem with modernising everything, and keeping it in sync, is that examples from examples' repositories are copied inline. This is problematic because updates to either page now require porting the work to the other repository.
Let's take /docs/Web/API/fetch#examples as an example.
The example is clearly copied inline as I claim:
https://github.com/mdn/content/blob/main/files/en-us/web/api/fetch/index.md?plain=1#L267-L290
So, for example, if we decided to update the example to use
async
/await
, then we would have to update both, that page, and the examples repository page: https://github.com/mdn/fetch-examples/blob/master/fetch-request/index.html.I'm proposing that this is possibly solved by using macros in the build process that reference the example repository file(s), inlining them for us.
Thoughts?
Alternative suggestions are welcome too - anything that can help mitigate the issue of maintenance in this area.
Beta Was this translation helpful? Give feedback.
All reactions