-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Custom Serve Executor Doesn't Respect Configurations #159
Comments
Hi @tommyc38 , thanks for reporting this. Could you share an example of your project.json with your extra configs here? That way I can look at making the executor more compatible. |
@simondotm below is a contrived example that resembles my project. Please don't hesitate to ask any questions and thank you for writing this lib! Project Structure:
|
The problem is this command:
Then you call like this where you are effectively hard coding the target and the command in:
I've just briefly looked at the code but it looks like we need to call the actual ExecutiveContext properties (e.g. target and target configuration) rather than the hard coded target and target options. Here is a link to the ExecutorContext Interface. |
@tommyc38 I'll take a look at this when I get a spare moment over the next week or so. 👍 |
@simondotm have you had a chance to take a look at this? |
@tommyc38 not yet unfortunately, slammed with work atm. On my radar though |
I have configurations for serve, watch, and the firebase targets. My configs for each are dev, prod, and local. The problem I am facing is that the serve target/executor doesn't respect any configurations under it. Is this by design or a bug?
The text was updated successfully, but these errors were encountered: