Task #10611

Story #10285: As Roger, I want clean and extensible JavaScript Code

Explore using JSON schema to document/test the registry.

Added by Sebastian Kurfuerst over 4 years ago. Updated almost 3 years ago.

Status:Resolved Start date:
Priority:Should have Due date:
Assigned To:Sebastian Kurfuerst % Done:

0%
Category:-
Target version:- Estimated time:0.00 hour

History

#1 Updated by Sebastian Kurfuerst over 4 years ago

  • Status changed from New to Accepted

#2 Updated by Sebastian Kurfuerst over 4 years ago

  • Status changed from Accepted to Under Review

#3 Updated by Rens Admiraal over 4 years ago

I know it's not meant for production environment yet, but just a question to open the discussion without taking a stand :)

Validation of the registry should be done before the registry is cached, or be done on cached parts of the registry before caching and on possibly non-cached (if possible in some situation) parts at runtime?

#4 Updated by Sebastian Kurfuerst over 4 years ago

Hey,

Validation of the registry should be done before the registry is cached, or be done on cached parts of the registry before caching and on possibly non-cached (if possible in some situation) parts at runtime?

right now, I see it more as a documentation tool which we use to express how the registry should look like and what contents it should have -- somehow like an executable specification.

So, I'd imagine that module would be only active on Development time, and would check the compiled contents of the registry.

I'm not sure I answered your question, does that make sense?

Greets, Sebastian

#5 Updated by Robert Lemke over 4 years ago

  • Status changed from Under Review to Resolved
  • Estimated time set to 0.00
  • Remaining (hours) set to 0.0

#6 Updated by Robert Lemke almost 3 years ago

  • Project changed from Base Distribution to TYPO3.Neos

Also available in: Atom PDF