wrhn

Recent submissions

Comment · 3 months ago
What if we made a mistake by introducing and generalizing the concept of the "Controller" ?

They are boilerplate, they spread logic in multiple places and last but not least, they make testing very cumbersome.

Comment · 3 months ago
No, nothing to install on your server. Everything is done via SSH from your phone and the server, there is nothing in-between. When you first SSH into the server, the key is stored in your keychain and reused for these operations. This way, you don't have to enter it everytime, but it's still safely stored.
Comment · 1 year ago
You did a really great job describing the project and documenting it in the README. Congrats. The project looks super clean and professional.

That being said, TBH I don't see any real scenario where I would "prototype a CLI". Unlike a GUI where elements can be placed in some places vs others, a CLI is a CLI.

For any developer, it would probably take less time to write it directly using one of the libraries listed here : https://bloomberg.github.io/stricli/blog/intro (TS/JS) or https://github.com/spf13/cobra (Go) with stub implementations for commands.

The main problem for me is that defining the CLI in a JSON file lacks all the flexibility of code (reusability, etc.).

Comment · 1 year ago
Based on your feedback, I've released v0.4.0.

It includes a simple react-native target to show how to do it. To make things easier to understand, I've also revamped the documentation, added a Guide to create your own target and enhanced the Tutorial with a RN target.

Finally, I've added the Tutorial code in the repo for whoever wants to browse it without necessarily performing all the steps.

Thanks a lot again for your feedback. My email is open :)

Comment · 1 year ago
I like the idea of using one's native language and Portuguese is not far from mine so I kind of understand the README. But unfortunately, it is what it is, providing it in Engligh would probably make it more accessible to the HN community.
Comment · 1 year ago
Let's take the first example here : https://ui.shadcn.com/docs/components/dialog. In this case, you have only one UC named EditProfileUCD, with the following input => name: PersonFullname and username: Username. All the things related to "UI" are not use cases since they are specific to a GUI target. A good tip to see if something is a UC or not : it should be available on all platforms. Opening a dialog in a Terminal is not for instance.

To continue with this example, you would add a <UCEntrypoint uc={uc} /> in your webpage, referencing EditProfileUCD. According to the client policy defined in the UCD and the UC auth, the button "Edit Profile" will show up or not. You can also simply disable it.

And your Dialog would render a <UCPanel uc={uc} /> that will display the form based on the UC input. Check out the contract of UCPanel (https://github.com/c100k/libmodulor/tree/master/dist/esm/tar...) to see how you can design the form and the form fields. Ideally, you would design these only once, and use <UCPanel uc={uc} /> across your whole codebase.

> said in another way: many of the people on HN have a backend api, a react SPA, and a mobile app. what types of problems do i have now which libmodulor solves?

In this typical architecture, you would benefit a lot from libmodulor. All your business functionality would be expressed as individual use cases, organized in apps corresponding to your business domain. You would have a server target (backend api), a react-web target (react SPA), a react-native target (mobile app). Each of them will bind the appropriate things in their container. The API endpoints will be automatically mounted in your backend API. They correspond to UCDs having a server lifecycle. Adding a <UCPanel uc={uc} /> in react web or react-native will render the same UC for each platform and submit it automatically to the server, without you having to do any plumging whatsoever. You are totally free to expose a UC in web but not in react-native.

> do i get a mono-build-system, where everything flows together and i just say "libmodulor build" and "libmodulor deploy" and I'm good to go?

This is clearly an important part that is non-existent at this time. For my own products for instance, I deploy each based on the target used (push on a PaaS for a server target, webpack/vite for a web target, fastlane for a react-native target, etc.)

If you have some time, I highly recommend to follow the "Getting Started", showing you how you can multiply the targets, re-using the apps as is.

Thanks a lot for your questions, they help me a lot to see where I fail to explain and how I can simplify things.

Comment · 1 year ago
> it wasn't clear how each of those translates to TypeScript

That's a fair point. I will add more details on how each of these notions translates to TypeScript. Quickly :

  - UseCase : a file containing the use case definition
  - App : a directory with a use cases folders and metadata (i18n, metadata)
  - Product : a directory with a apps folders and metadata (i18n, metadata)
  - Target : depends on it by for a GUI it's the screens where use cases are injected
> I would rethink how you named the 'App' layer

I'm not a huge fan of this name either, but couldn't come up with something better at this time. `Module` seemed to broad to me. Although the notion is not totally clear to you, do you have any ideas in mind ?

I agree that it's not as straightforward as other solutions at this moment. I'll keep working and improving this to reduce the time needed to get started.

Comment · 1 year ago
I'm not sure there is a relation between a program/library to be "opinionated" vs the skillset of the person who created it.

In my case, I'm using the word because the library defines a set of rules and conventions to follow. They are indeed based on my experience.

Are they perfect ? Probably not. And I'm totally open to review them if I missed things. That's how we all learn. Like any model (in a mathematical way), it is an approximation of the actual problem.

Comment · 1 year ago
Looks great, will have a look at it.
Comment · 1 year ago
Thank you for your feedback, I really appreciate.

Let's say you want to create a product with auth and crud for contacts. You'll have a SignInUCD, a CreateContactUCD, a AddPhoneNumberToContactUCD, etc.

As you said, your react-native target will define the UI screens. You are free to design them the way you want as the library does not make any assumptions about the UI/UX. In every screen where you want to "inject" a use case, you'll use the `useUC` hook and `<UCPanel uc={uc} />` (see https://github.com/c100k/libmodulor/tree/master/dist/esm/tar...). See also https://github.com/c100k/libmodulor/blob/master/docs/getting.... It explains for web, but the mechanics are the same.

Since react-native expects `<View>`, `<Text>` and not `<div>`, etc. you'll also need to define your "design system", like it's been done here for example : https://github.com/c100k/libmodulor/tree/master/dist/esm/tar.... Basically, you need to define how you want a use case form to be displayed, etc. When in web we rely on `<input>`, in react-native we'll rely on `<TextInput>`. And of course, according to the data type, you can display a specific form control.

I realize it's super hard to explain and I'm not clear enough but hopefully I'll find the best way to express it.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton