-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support remembering previously completed Verb Installations #2070
base: master
Are you sure you want to change the base?
Conversation
- add a label that informs the user if a verb is already installed - add a method to the VerbsManager to check whether a verb has already been installed
I agree. A |
I thought about adding a new script to What do you think? |
Why should it be a script and not in Java? |
That is a good point. It doesn't need to be a script it could also be implemented in Java. For me it is more intuitive to implement it in Java because we will access the |
Did you really mean "implement it in Java" or "implement it in Javascript"? |
implement it in JavaScript |
Ok, then the sentence makes more sense. Nevertheless, for me this should be in Java because it's nothing you would want to influence with custom scripts (it's similar to e.g. |
So basically you would add the two methods to a new with I.e.: @Safe
public class VerbUtils {
void registerVerb(String verbId) {
...
}
boolean isVerbRegistered(String verbId) {
...
}
} |
Yes, something like that. We can decide if it belongs more to a verb or to a container. |
I have some problems getting the container information based on its name/id... In a nutshell I want to add the following class to package org.phoenicis.tools.container;
import org.phoenicis.configuration.security.Safe;
@Safe
public class ContainerUtils {
void registerVerb(String containerId, String verbId) {
...
}
boolean isVerbRegistered(String containerId, String verbId) {
...
}
} The first thing I need to do for both methods is fetching the content of the |
Why don't you put it to |
Do we have @safe accessible from |
From my understanding, @qparis intention was to always put the JS API into the package where it belongs logically (and not all API together in one place). So yes, this should be possible. |
I think that it may be a good idea to wait with this PR until we have changed the repository structure to a more flexible one (I can't find the corresponding issue). Afterwards I think it will also be easier to fetch an entity (i.e. application, script, container etc.) for a given id/name. This should solve a lot of the problems I have in this PR. |
Ok. |
This PR does the Phoenicis part discussed in #1824.
I'm not sure yet whether we want to add the new methods
registerVerb
andisVerbRegistered
to the engine class, because they seem somehow unrelated to the engine to me.