chore(build): map dev env to environment.ts

[filipesilva]

By mapping --env=dev directly to environment.ts we can avoid having an extra file that is never really used.

[hansl]

LGTM!

[radoslavpetranov]

Wasn't the idea of having environment.prod.ts and environment.dev.ts to allow the build script to copy the correct file onto environment.ts which in turn is the file referenced in our code

import { environment } from "../environments/environment"

Am I misunderstanding something? Is there a way to import the correct file (that depends on the env variable specified during the build process) into our code right now?

[hansl]

Yes. Same as before, except now environment is also dev. So in development we don't replace it, while in prod (or others) we replace it with the proper environment.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}