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

Error while targeting es2017 #3011

Closed
ig-robstoffers opened this issue Nov 13, 2018 · 4 comments · Fixed by #3151
Closed

Error while targeting es2017 #3011

ig-robstoffers opened this issue Nov 13, 2018 · 4 comments · Fixed by #3151
Assignees
Labels
🐛 bug Any issue that describes a bug 🔥 severity: high 🛠️ status: in-development Issues and PRs with active development on them version: 6.2.x

Comments

@ig-robstoffers
Copy link
Contributor

Description

Created a brand new Angular project and changed the target in the tsconfig.json file to es2017. After attempting to add an igx-input-group the following error is displayed in the chrome developer console:
image

Changing the target back to the default es5 value causes everything to work as expected.

  • igniteui-angular version: 6.2.0
  • browser: Chrome 70.0.3538.77

Steps to reproduce

  1. Extract attached sample
  2. Run npm install
  3. Run npm start
  4. Open site in browser and look at dev tools console.

Result

What is the actual result after following the steps to reproduce?

IgxCalendarDateDirective is not defined error is shown

Expected result

What is the expected result after following the steps to reproduce?

No error is shown and the Input component is rendered.

Attachments

input-sample-seven.zip

@ig-robstoffers
Copy link
Contributor Author

Just a note, I only tested this against the Input Group component but not all the other components so it's possible the other components may have similar issues as this one.

@grosch
Copy link

grosch commented Nov 13, 2018

Definitely looking forward to this one being fixed!

@QuinntyneBrown
Copy link

This is also happening when targeting es2015

@mpavlinov mpavlinov added 🛠️ status: in-development Issues and PRs with active development on them and removed 🆕 status: new labels Nov 23, 2018
@damyanpetev damyanpetev self-assigned this Nov 23, 2018
damyanpetev added a commit that referenced this issue Nov 26, 2018
Use base class or a token/interface combo for DI child components to
avoid Circular dependency warnings and compilation errors in targets
es2015 and newer. Added explicit constructors in extending classes as
DI metadata doesn't get added otherwise (subject to fixes in ng compiler)

Also resolved some general circular refs and updated
tests that wouldn't work with es6.

Affected: list, calendar, combo, input-group, drop-down, expansion-panel,
grids, tabs, time-picker
damyanpetev added a commit that referenced this issue Nov 26, 2018
Use base class or a token/interface combo for DI child components to
avoid Circular dependency warnings and compilation errors in targets
es2015 and newer. Added explicit constructors in extending classes as
DI metadata doesn't get added otherwise (subject to fixes in ng compiler)

Also resolved some general circular refs and updated
tests that wouldn't work with es6.

Affected: list, calendar, combo, input-group, drop-down, expansion-panel,
grids, tabs, time-picker
damyanpetev pushed a commit that referenced this issue Nov 26, 2018
kdinev pushed a commit that referenced this issue Nov 26, 2018
* refactor(es6): resolve es6+ compile errors and most circular deps #3011

Use base class or a token/interface combo for DI child components to
avoid Circular dependency warnings and compilation errors in targets
es2015 and newer. Added explicit constructors in extending classes as
DI metadata doesn't get added otherwise (subject to fixes in ng compiler)

Also resolved some general circular refs and updated
tests that wouldn't work with es6.

Affected: list, calendar, combo, input-group, drop-down, expansion-panel,
grids, tabs, time-picker

* fix(hammer-configs): Add  Injectable DatePicker/TimePicker HammerConfigs. #3011

(cherry picked from commit 59aed5e)
@kdinev
Copy link
Member

kdinev commented Nov 27, 2018

@ig-robstoffers @grosch @QuinntyneBrown We made the fix available in 6.2.1 and in 7.0.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Any issue that describes a bug 🔥 severity: high 🛠️ status: in-development Issues and PRs with active development on them version: 6.2.x
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants