Project status / where is the source?

[franleplant]

Hi Guys! Just by chance I remembered about this project and just by chance I was going to look at the source but couldn't find it. Am i missing something obvious?

Well, as far as my exhausted Saturday night brain can understand you guys for some reason ignored the source code in this PR #34 , why? how did you develop further features after that?

Also, just wanted to know what's up with the project and with you @gillchristian :)

cheers!

[gillchristian]

Hi Fran! :wave:

Well, as far as my exhausted Saturday night brain can understand you guys for some reason ignored the source code in this PR #34 , why? how did you develop further features after that?

It's been a while since we were working on it, I assume I just kept working on the code locally but really I don't have a clue of why besides that it was a mistake :thinking: :facepalm:

Nice catch! I'll see if I can revert it to a working state.

what's up with the project

@fvictorio and I developed an MVP (before deleting it :trollface:) and lost the interest after that. I think in practice it wasn't as useful as we thought. But it would be nice to give it a second chance. I've been doing TypeScript at work for a while already, maybe type checking is something that would make more sense than running the code, or even both. Wdyt?

[franleplant]

Wow, I neglected this email for too long. I think that typechecking example code would be awesome.

I am also super into typescript, check out my blog https://nosleepjavascript.com/ it is basically typescript heave ajajaja.

A couple of things that made this project a bit less interesting to participate for me were a couple of particular choices that I still don't think they are particular useful besides experimenting with them:

• the use of rambda instead of regular js/ts
• the complex cli approach

I love the prettier mind-set start doing one thing well with as little config as possible and then start adding as it becomes necessary, perhaps a simpler version of this lib would

• extract all codeblocks labeles as javascript or typescript code
• put the code into myApp/chimi_tmp/codeblock_1.test.{ts,js}
• leave everything else up to the consumers:
  • wrapping code i.e. describe blocks
  • typechecking it
  • compile it with babel (babel 7 has out of the box support for typescript, flow and of course js)
  • include it in the test pipeline with any test runner they might be using

So in that sense this becomes just a codegen tool (similar to graphql codegen et all) that only generates code, and then the consumer is responsible for using that code.

And so by doing that you can have a simpler product that can be production ready.

Another alternative could be thinking about this the other way around, why instead of extracting codeblocks from markdown into regular js/ts files, we do put regular ts/js file's content into our markdown.

I've done this in some personal projects:

{{myfile.ts}}

you could even add line specifiers in the syntax.

Perhaps there's some markdown plugins that already do that? but also the markdown engines tend to be native github/bitbucket/whatever that AFAIK are not configurable so having a very little utility tool that does this might be a good way of achieving similar results.

Fran

On Mon, Jun 22, 2020 at 1:40 PM Christian Gill [email protected] wrote:

Hi Fran! 👋

Well, as far as my exhausted Saturday night brain can understand you guys for some reason ignored the source code in this PR #34 https://github.com/Huemul/chimi/pull/34 , why? how did you develop further features after that?

It's been a while since we were working on it, I assume I just kept working on the code locally but really I don't have a clue of why besides that it was a mistake 🤔 🤦

Nice catch! I'll see if I can revert it to a working state.

what's up with the project

@fvictorio https://github.com/fvictorio and I developed an MVP (before deleting it [image: :trollface:]) and lost the interest after that. I think in practice it wasn't as useful as we thought. But it would be nice to give it a second chance. I've been doing TypeScript at work for a while already, maybe type checking is something that would make more sense than running the code, or even both. Wdyt?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Huemul/chimi/issues/59#issuecomment-647637433, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOEIJY2NTE5DO4GRROSHHDRX6CQ3ANCNFSM4NDGCXYA .