TrizTech/ohif-viewer
17
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(spelling): Add codespell config + github action, run and fix a good number of typos (#3645)

Browse Source
This commit is contained in:
Yaroslav Halchenko authored and GitHub committed 2023-09-12 07:40:38 -04:00
1 parent 64079e0720
commit 11ca5b6eae
76 files changed
+128 -100
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

platform/docs/versioned_docs/version-1.0-deprecated/faq/technical.md
+1 -1
View File
@@ -5,4 +5,4 @@ At the time of project conception, Meteor was a simple way to begin using bleedi
## Do you have any plans to stop using Meteor?
We have considered migrating templates from Blaze (http://blazejs.org/) to React (https://reactjs.org/) or Vue (https://vuejs.org/), simply because these decouple the view layer from the remainder of the application. Blaze currently lacks [Stand-alone Support](http://blazejs.org/#Better-Stand-alone-Support) which means that our templates are not re-usable outside of a Meteor application. This is certainly a downside, but the resource cost to migrate every template is significant.
We have considered migrating templates from Blaze (http://blazejs.org/) to React (https://reactjs.org/) or Vue (https://vuejs.org/), simply because these decouple the view layer from the remainder of the application. Blaze currently lacks [Stand-alone Support](http://blazejs.org/#Better-Stand-alone-Support) which means that our templates are not reusable outside of a Meteor application. This is certainly a downside, but the resource cost to migrate every template is significant.