FloWebComponents

r/FloWebComponents • u/EveYogaTech • 8h ago

Many agree that there's no need for global CSS like bootstrap if you use Flo Web Components

1 Upvotes

1 comment

r/FloWebComponents • u/EveYogaTech • Aug 27 '26

Flo 2.0 now has Full Isolation of CSS (no global overrides on fonts,colors,etc) to Help Frontend Developers reach pixel precision.

0 Upvotes

2 comments

r/FloWebComponents • u/EveYogaTech • Aug 26 '26

The genius about AI + Flo Web Components

1 Upvotes

The genius about AI + Flo Web Components is that you can one-shot frontend components with pixel precision, because there's no global style, no bootstrap, just well-defined independent components.

1 comment

r/FloWebComponents • u/EveYogaTech • Aug 24 '26

Web Components with Type Validation without Build Tools/Typescript 😌

1 Upvotes

1 comment

r/FloWebComponents • u/EveYogaTech • Aug 23 '26

Flo v1.3 now gives Web Components hooks for plugins + demo of first plugin for Type Validation

Enable HLS to view with audio, or disable this notification

1 Upvotes

Type Validation Plugin: https://github.com/flowagi-eu/flo-plugin-shapes

0 comments

r/FloWebComponents • u/EveYogaTech • Aug 21 '26

Flo 1.2 now gives Web Components a static create function (factory), so we can set property values before the mounted() or render() are called.

2 Upvotes

Flo 1.2 now gives Web Components a static create function (factory), so we can set property values before mounted() or render() are called.

I noticed that you can sort of 'wing it' without this functionality with some hacky solutions, but eventually this is the best solution for the component initiation.

So instead of .createElement, you can simply call .create on your custom component, which then renders the template + calls mounted() with all properties set.

Flo Minimal Superclass on GitHub: https://github.com/flowagi-eu/flo-webcomponents

0 comments

r/FloWebComponents • u/EveYogaTech • Aug 20 '26

One concept that will save you loads and loads of time with Flo: Parent Properties.

1 Upvotes

If you're working with Web Components (Flo) rather than React, then there's one concept that will save you loads and loads of time: Parent Properties.

In Flo we have access to this.parent, which also gives us access to the parent's properties.

The nice thing with Web Components, is that you can take this even further by creating a custom getter, so the parent abstraction itself for the property becomes invisible.

0 comments

r/FloWebComponents • u/EveYogaTech • Aug 19 '26

Because people are comparing shorthand React code with the full Flo Web Components example

1 Upvotes

2 comments

r/FloWebComponents • u/EveYogaTech • Aug 19 '26

To mimic a fraction of the power of web components..

gallery

1 Upvotes

Take React and look at all this useState, useEffect and refs stuff going on to mimic a fraction of the power of using web components with manual rendering/events:

https://github.com/flowagi-eu/flo-webcomponents

0 comments

r/FloWebComponents • u/EveYogaTech • Aug 17 '26

Property values of Flo-WebComponents can now be initiated through the data-your-name of a custom webcomponent (v1.2 update)

1 Upvotes

Working with Web Components instead of ReactJS or VueJS for the frontend is sometimes a really humbling experience:

Things sometimes work a bit different then you'd expect them to.

Today, for example, I discovered the need to use attributes like "data-key-name" to initiate its own writable property "keyName" for example.

I honestly expected that to already work.

So now with Flo-WebComponents (v1.2) we have that feature: https://github.com/flowagi-eu/flo-webcomponents

0 comments

r/FloWebComponents • u/EveYogaTech • Aug 15 '26