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

Remove Aurelia from the class name to be consistent with other module implementations #109

Open
nuxy opened this issue Apr 23, 2018 · 1 comment

Comments

@nuxy
Copy link

nuxy commented Apr 23, 2018

This is more of a nit-pick and nice-to-have, if anything.

  • We know this module is specific to the Aurelia framework.
  • We know it cannot be used in anything other than the Aurelia framework.
  • Could we please omit Aurelia from the module class name?

It would be nice to be able to just do:

import {Configuation} from 'aurelia-configuration';

vs

import {AureliaConfiguration}                  from 'aurelia-configuration';
import {AureliaConfiguration as Configuration} from 'aurelia-configuration';
@Vheissu
Copy link
Owner

Vheissu commented Dec 2, 2018

Agreed and this is a change that is coming in a next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants