react-dsfr VS compodio

GitHub Repo: https://github.com/codegouvfr/react-dsfr Storybook: https://react-dsfr-components.etalab.studio/?path=/story/%F0%9F%87%AB%F0%9F%87%B7-introduction--page

Great, don't hesitate to reach out in the discution section of the github repo. I love sharing my tips. https://github.com/codegouvfr/react-dsfr/discussions

My advice if you don't have a multi-million budget and you only need to support React is to start from MUI components. Components like Date pickers, or Autocomplete are complex and time consuming to code from scratch. First thing you want to do is to build a custom theme for MUI (example DSFR, Example OnyxiaUI) this will make the MUI components roughly match your design system out of the box. Then you can create your own components that are wrapper around MUI components and customize them until they match your design (Example). Trust me, we always underestimate the complexity of building base component from scratch. There are tons of things to consider, I don't even mention the accessibility concerns... Customizing MUI components is the quick win route.

Thank you ☺️ I mean it's open source so technically you can but legally you can't. If you publish a website using this lib you'll get it shut down by the French authorities.

If you want a real-world use case you can consider this function, it has a very opaque and complex return type that is inferred from the input it receives. Having type-level unit test for this function is very useful both for ensuring the return type is inferred correctly and as an implicit documentation.

Do you think it's totological to test the return type of this function?

Take for example this function, it's return type if very opaque. I'm very happy I'm able to test it.

This is much less precise than what my return type inferred from what the user gives me as input.

Currently working on compodio in my free time. A website that makes it easier to find, and subscribe to community radio shows as a podcast. It uses NextJS, Python, PHP, MySQL

I used it here in a function that constructs a string of hex colours for a css gradient from an array. I spend more time in python than JS, and looking at this code again now I see it certainly isn't perfect.

I feel like now that I'm developing mostly with react, which has everyone rethinking how to think about separation of concerns, I'm still figuring things out again. In a current project, I have global styles sheets for the site as a whole, then I try to bundle css modules for components of a site in a folder with other files related to the component (ex. a main menu component). The aspiration being that some components will be generic enough that I could just copy one folder and have everything I need (css, js, etc) to add that feature to another project.

Impressive. I've been working on something similar, but much simpler. I settled for just organizing colours by lightness. I just might borrow your ant colony optimization.

This is an in progress component I'm working on that always expects to receive an array of available image sizes, that jpg/webp are always available.

I'm not sure if a working example of something similar from one of my own projects would help. The code here, it what I used to scrape all the elements with the archiveList-post class from this page.

Then You can pretty much do the same thing I did with the next page link here.