Hot answers tagged

3

This is related to constraint-programming. Prolog is an example of such a system. There exists javascript implementations of prolog http://yieldprolog.sourceforge.net/ . You could then make your prolog program and use it on both the server and client. Another approach is having all the logic on the server side but expose it as an api which the client could ...


2

If what you are trying to do is present a single endpoint to many APIs, you might find some value in Netflix' Falcor project. Falcor is not a query engine. It is a library for "efficient data fetching." It is one example of a growing set of tools delivering "Demand Driven Architectures" -- alternatives to traditional rest services that allow the author of a ...


2

This isn't really specific to Scala DSLs. You have the same problem with the traditional Builder pattern, when you want a builder that needs to be given certain things. Instead of execution order it is then a dependency. For example, you want a builder that can build either ProductA or ProductB, but when you choose ProductA you must specify a delivery ...


1

Are there any other problems, aside from the mentioned data consistency issue, I should be aware of when I save data like this in a relational database? Source control. Is there a better option for persistence? Maybe? I mean, what you're talking about is scripting. Normally, scripts are deployed alongside the app and follow the more traditional ...


1

Yes, there is exactly that. You can provide your quickfix as a semantic modification to the EMF resource. Xtext's serialization mechanism will figure out how to convert your changes to the AST back to text. Something along these lines should do the trick: @Fix(MISSING_SUPERTYPE_ID) public void fixupSupertype(final Issue issue, IssueResolutionAcceptor ...



Only top voted, non community-wiki answers of a minimum length are eligible