πŸ‡ΊπŸ‡ΈUnited States @eswiderski

Account created on 23 October 2005, over 18 years ago
#

Recent comments

πŸ‡ΊπŸ‡ΈUnited States eswiderski

@dqd yes, it still applies to 2.0-dev

πŸ‡ΊπŸ‡ΈUnited States eswiderski

eswiderski β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States eswiderski

Ahh, ok thank you! I was still using 1.2.x-dev.

πŸ‡ΊπŸ‡ΈUnited States eswiderski

Ok, was it merged into 1.1.x-dev and 1.2.x-dev? I'm not seeing any difference behavior in 1.1.x-dev.

πŸ‡ΊπŸ‡ΈUnited States eswiderski

Can we merge this into one of the newer dev branches?

πŸ‡ΊπŸ‡ΈUnited States eswiderski

@jurgenhaas you rule!

πŸ‡ΊπŸ‡ΈUnited States eswiderski

This module destroyed a bunch of my custom menus. STAY AWAY.

πŸ‡ΊπŸ‡ΈUnited States eswiderski

Agree @jurgenhaas.

@mxh It seems like we'd be limiting ECA's scope just for this use case. If a vision for ECA is to indeed empower non-developers and alleviate custom development, then this would be extremely powerful. Personally, ECA has already allowed me to eliminate 30-40 modules. But also realize the project needs some guardrails.

That stated, ECA is life-changing without this capability...and completely respect both of your pov's. Just my $0.02.

Production build 0.69.0 2024