Schema-based Data Validation

[tamaracha]

Hi,

first, I have to say thank you for this project and the thoughts its motivation originates from.

Not sure if this is the right place for sharing, but yesterday, this article found the right words for my uncertain feeling of being gaslighted. This feeling is not new, and it is not limited to Tailwind CSS. Actually, I was doing some research on Tailwind's impact on A11Y, I am a blind A11Y Consultant. My practical observation is that A11Y suffers from JS people doing everything on their own (design, UX, build tooling). A11Y is not just about design. The behavior part might be even more critical, at least for interactive controls. If you have to build a custom control like a multi-select with adjusted UX behavior, you have various tasks:

1. Model its behavior and logic as an abstraction (also good for testing)
2. Find a good HTML structure, bind it to the model (reactivity), properly tie the ARIA attributes and roles together if necessary
3. Don't forget to connect user interactions with model commands/actions (keyboard navigation, focus management). Really, getting this right is so underrated.
4. Add eye-assisting styles. We could even use ARIA and roles as CSS selectors, so these belong to the semantic fundament instead of a redundant afterthought.

This covers such a broad range of skills and knowledge, and I see so much stuff out there where each of these areas sucks (built with Tailwind and React). Besides, listening to my screenreader reading all these class names in the HTML structure drives me crazy.

Reading through the discussions about Tailwind pros and cons, I encountered so many strange fallacies, strawman arguments, false dilemmas, moving goalposts, and so on.

• „SOC is a myth/cult, because software parts are never fully decoupled.“ (strawman and misconception of SOC, SOC is about working together with minimal friction, not about total decoupling)
• „Semantic Cult“ (poisoning the well)
• „Skepticals are toxic or narrow-minded“ (ad hominem, self-victimization)
• For A11Y, the docs recommend inserting hidden span elements without mentioning aria-label, aria-description, or title attribute. Okayyy, now I know where all these chatty spans come from.
• There is @apply, but the docs discourage its usage. In practical examples, it doesn't work reliably, and each discussion around this ends with „The creator doesn't recommend it“ (argument from authority).

Your article about misinterpreted visual abstraction and over-emphasized dry principle was my missing link. As a non-technical metaphore, I could begin with the widely accepted consens that we should try to be honest. In the next step, I could over-emphasize this to conclusions like „Being kind is evil“ or „Holding back information is evil.“ I think it was Zuckerberg who argued that we should give up data protection and privacy, because hiding information is evil. Is there something like Bullshit Fatigue …

Sorry for the long introduction. Now my actual question: I'd like to have data validation and itellisense for YAML (meta)data, e.g. based on JSON schema (no typescript). Is something like this planned for Nue, or should I try to figure it out myself? When I taught researchers data literacy, I created data schemas for them and onboarding was much easier with such tooling that nudges people in the right direction (confidence).

[tipiirai]

Haha. Quite an intro indeed! Loved it. Always great to hear that I'm not alone here to value solid software engineering patterns in the frontend. The gaslighting of the industry is so effective that these are rare takes. It's both sad, but also a huge possibility because ultimately, you can make significantly better sofware with web standards and timeless patterns.

When it comes to YAML, I have some plans to implement a new parser that fixes all the issues on the current specs, or more specifically: fixes all the issues on how TypeScript developers frame it on their minds being the worst thing for data ever.

[nobkd]

It may not be properly reflected in the docs, but someone submitted a json schema (at least for parts) of nue's config. I'm also not sure, if this was what you were after. See #408 and SchemaStore/schemastore#4218

[tamaracha]

Thanks, that's the right direction. ;-)