WasmEdge
Feature Request: An efficient way to update WasmEdge's version
Is your feature request related to a problem? Please describe.
When WasmEdge has released a new version, we should ensure everything in this doc uses the latest version of WasmEdge.
There are 12 files that need to be synced with the latest version of WasmEdge. It would be complex to maintain all 12 files.
Describe the solution you'd like.
Can we think of a simple way to update the version of WasmEdge? For example, we can first set a general parameter called {{ wasmedge_version }}. Then we update ``{{ wasmedge_version }}` equals the latest version of WasmEdge. Finally, all the docs are using the same and lastest version of WasmEdge.
This would be much easier to update WasmEdge's version. Any feedback is welcome.
Describe alternatives you've considered
No response
Additional context.
No response
Can we think of a simple way to update the version of WasmEdge? For example, we can first set a general parameter called
{{ wasmedge_version }}. Then we update ``{{ wasmedge_version }}` equals the latest version of WasmEdge. Finally, all the docs are using the same and lastest version of WasmEdge.
Yes it's a good approach I was thinking of a build step where it scans all files and replaces that word with a version number specified using sed[0] or other similar tool.
- https://www.gnu.org/software/sed/manual/sed.html
I do not have any idea about what could solution be, but am happy to help if I could!
@alabulei1 Are the docs not going to be updated for different versions/releases? If we are, then we can easily change the variable value at any time. Please correct me if I have misunderstood the feature.
Can we think of a simple way to update the version of WasmEdge? For example, we can first set a general parameter called
{{ wasmedge_version }}. Then we update ``{{ wasmedge_version }}` equals the latest version of WasmEdge. Finally, all the docs are using the same and lastest version of WasmEdge.Yes it's a good approach I was thinking of a build step where it scans all files and replaces that word with a version number specified using sed[0] or other similar tool.
- https://www.gnu.org/software/sed/manual/sed.html
This sounds good! A tool like this can reduce human errors
@alabulei1 Are the docs not going to be updated for different versions/releases? If we are, then we can easily change the variable value at any time. Please correct me if I have misunderstood the feature.
@hydai @juntao What do you think? I think we use this way when 1.0 is released.
Yup something like-
Could be very useful for onboarding developers!
@alabulei1 Are the docs not going to be updated for different versions/releases? If we are, then we can easily change the variable value at any time. Please correct me if I have misunderstood the feature.
@hydai @juntao What do you think? I think we use this way when 1.0 is released.
The 0.x series changes API a lot between versions, and it would be better to have it right now. As you can see here, we already split the API reference during different versions.
Just to add on:
Source: https://docusaurus.io/docs/versioning
The 0.x series changes API a lot between versions, and it would be better to have it right now. As you can see here, we already split the API reference during different versions.
We can tag this version for now and set disableVersioning and enable it in future.
I find how to pass env var in docusarus V2. This will fix this issue faster. https://stackoverflow.com/questions/61127010/how-to-pass-env-var-to-docusaurus-v2
Feature Request: An efficient way to update WasmEdge's version
https://github.com/WasmEdge/docs/issues/53
The central problem discussed in the GitHub issue is the difficulty of efficiently updating the version of WasmEdge in the documentation. The proposed solution is to use a general parameter called {{ wasmedge_version }} and update it to the latest version using a build step tool like 'sed'. This approach would simplify the process of maintaining and updating the version of WasmEdge in all the documentation files. Other suggestions include using versioning tools like Docusaurus and passing environment variables to Docusaurus V2.
this result is generated by flows.network. Triggered by @alabulei1