Conversation
|
i wonder if we should just have a we generally do one-to-one docs so we can show migration examples (rich diffs). but in this case, there are no diffs, rather just basic examples. so we probably could have one doc thoughts? would be nice to get the opinion of someone like @outslept or @Fuzzyma too |
|
It depends how the files are consumed but afaik all the markdowns are only redacted and read by people so it doesn't have to follow a strict format. |
|
they ultimately will be synced into the e18e site pretty much. so yes, its just a human readable thing, i.e. nothing programmatically expects any particular structure if we're all happy having one fetch doc, we should probably unify axios in this PR too (just rename the axios doc to |
|
Okay will do it tomorrow guys 💪 |
ff3efb4 to
be4e0d4
Compare
be4e0d4 to
c9ec89d
Compare
Adding node-fetch and cross-fetch to the module replacements, with this we have modules that will require the same replacements how should we share that part ? Should we do it like lodash/underscore example ?
I also created issues in the respective repositories as it would be nice to warn users about not needing the modules depending on their engines:
node-fetch/node-fetch#1857
lquixada/cross-fetch#209
Closes #269 #268