Skip to content
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

build: add support for environments #50

Closed
dsebastien opened this issue Mar 1, 2018 · 1 comment · Fixed by #454
Closed

build: add support for environments #50

dsebastien opened this issue Mar 1, 2018 · 1 comment · Fixed by #454

Comments

@dsebastien
Copy link
Contributor

dsebastien commented Mar 1, 2018

Assuming the build specifies the environment (either default value or provided as CLI argument), make sure we have support for finding out the current environment within Stark apps (programmatically)

This requires some cleanup as we currently have (at least) these:

  • webpack options
  • Define plugin
  • src/environments/environments.ts: provides programmatic checks (if env === ...)
  • custom-typings.d.ts: probably doesn't need any typings for the env anymore!
  • HTML templating
  • polyfills.browser.ts
@dsebastien dsebastien added this to the 10.0.0-alpha.1 milestone Mar 1, 2018
@dsebastien dsebastien modified the milestones: 10.0.0-alpha.1, sprint 1 Mar 19, 2018
@dsebastien dsebastien added the P1 label Apr 24, 2018
@dsebastien dsebastien modified the milestones: sprint 1, 10.0.0-alpha.3 May 8, 2018
@Mallikki Mallikki self-assigned this Jun 12, 2018
Mallikki added a commit to Mallikki/stark that referenced this issue Jun 13, 2018
Mallikki added a commit to Mallikki/stark that referenced this issue Jun 14, 2018
Mallikki added a commit to Mallikki/stark that referenced this issue Jun 14, 2018
@christophercr christophercr reopened this Jun 18, 2018
@christophercr
Copy link
Collaborator

Re-opened this issue since it is not completely solved.

Currently it is not possible to programatically check the current enviroment in the stark packages, only in the client application (i.e. starter or showcase).

christophercr referenced this issue in christophercr/stark Jun 20, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 20, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 21, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 21, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 21, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 21, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 22, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 22, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 22, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 22, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 22, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 26, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 26, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 26, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 26, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 26, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 26, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 26, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
christophercr referenced this issue in christophercr/stark Jun 26, 2018
…importing environment.ts file) and at compilation time (using webpack Define plugin)

ISSUES CLOSED: #50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants