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
Would like to leverage deno doc, deno fmt, deno lint agnostic of Deno projects.
Would like to be able to extend my own Rust CLI using the underline components from Deno
Intent
Would like to see Deno take some responsibility for bringing alignment around the JavaScript ecosystem by providing those CLI tools agnostic of Deno projects (as much as possible).
We are in the transition to leverage Deno for incoming projects over NodeJS, but realistically, we are not there yet, but we would like to stop the bikeshedding and misalignment around these tools, and be closer to "a way" to solve particular issues where freedom isn't that valuable, or in the worst case, would be much better to improve "a tool".
Thoughts
I am not that familiar with Rust, but it seems that the simple wrappers for the underline packages used in Deno CLI actually do some tedious stuff around matching files, and so on. Maybe keep raising the level of abstraction would be beneficial.
Also, I tried to use deno doc https://github.com/straw-hat-team/logger/blob/master/src/index.ts but didn't work
This discussion was converted from issue #8595 on December 12, 2020 13:15.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
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
-
Context
deno doc
,deno fmt
,deno lint
agnostic of Deno projects.Intent
Would like to see Deno take some responsibility for bringing alignment around the JavaScript ecosystem by providing those CLI tools agnostic of Deno projects (as much as possible).
We are in the transition to leverage Deno for incoming projects over NodeJS, but realistically, we are not there yet, but we would like to stop the bikeshedding and misalignment around these tools, and be closer to "a way" to solve particular issues where freedom isn't that valuable, or in the worst case, would be much better to improve "a tool".
Thoughts
I am not that familiar with Rust, but it seems that the simple wrappers for the underline packages used in Deno CLI actually do some tedious stuff around matching files, and so on. Maybe keep raising the level of abstraction would be beneficial.
Also, I tried to use
deno doc https://github.com/straw-hat-team/logger/blob/master/src/index.ts
but didn't work❯ deno doc ./src/index.ts Cannot resolve module "file:///Users/ubi/Developer/StrawHat/logger/src/logger"
Beta Was this translation helpful? Give feedback.
All reactions