-
Notifications
You must be signed in to change notification settings - Fork 7
Meta model processing algorithm
homedirectory edited this page Jul 18, 2023
·
2 revisions
On each processing round:
- filter inputs for meta-model candidates and generate a meta-model for each one
On the 1st processing round:
- after processing round inputs process
MetaModels
:- if it doesn't exist, then generate it
- otherwise, analyse it and potentially regenerate if any of the following holds:
- there are new meta-models to include
- there are inactive meta-models to exclude
Behaviour w.r.t to file events:
- Rename/Move: if source is meta-modeled, then a new meta-model is generated, and
MetaModels
is regenerated to include it. The old meta-model is ignored, butMetaModels
no longer includes it, which is caused by a lucky bug. - Delete: if source was meta-modeled, then the affected sources set will at least contain its meta-model, which will be deactivated, and
MetaModels
will be regenerated to exclude it. - Content change: if source is meta-modeled, then its meta-model is regenerated.
- New: if created source is meta-modeled, then meta-model is generated and
MetaModels
regenerated to include it.
Per aspera ad astra
- Web UI Design and Web API
- Safe Communication and User Authentication
- Gitworkflow
- JavaScript: Testing with Maven
- Java Application Profiling
-
TG Development Guidelines
- TLS and HAProxy for development
- TG Development Checklist
- Entities and their validation
- Entity Properties
- Entity Type Enhancement
- EQL
- Tooltip How To
- All about Matchers
- All about Fetch Models
- Streaming data
- Synthetic entities
- Activatable entities
- Jasper Reports
- Opening Compound Master from another Compound Master
- Window management test plan
- Multi Time Zone Environment
- GraphQL Web API
- Guice
- Maven
- Full Text Search
- Deployment recipes
- Application Configuration
- JRebel Installation and Integration
- Compile-time mechanisms
- Work in progress