-
Notifications
You must be signed in to change notification settings - Fork 133
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
Addon is unusable with Ember 2.15 #239
Comments
@onechiporenko I just attempted to upgrade to 2.15 and see why this issue was created. Do you know what in 2.15 broke this add-on? I'd like to help if possible but at the moment there isn't a clear error indicating where this add-on is failing. What I am seeing is empty rows in the table and an error being thrown on click.
|
@onechiporenko Adding the following issue so it can be tracked. I believe this is related to the breakage of this add-on in 2.15. |
Hi, @steverhoades. Something become broken with partials on Ember-2.15. Since Ember core-devs recommended to not use partials and move to the contextual components I have to do this too. Branch v2.0 (https://github.com/onechiporenko/ember-models-table/tree/v2.0) contains new version of |
I now it is still WIP, but may I recommend that you nest the components? I think that would make it easier to grasp & to override it. E.g.: components/models-table.js You can use these nested components normally in the template, e.g. |
@mydea, thanks. I think I'll do as you said. It's a good idea! |
Awesome! Is there a place for recommendations etc, or should I just put them here? |
Yes, you may put it here.
Thanks! For now I need a "fresh outlook" (IDK, if it's a correct translation from "свежий взгляд со стороны"). "Coding part" contains next items:
|
I'm really glad that |
The discussion here has left me a little confused. Glad to see 2.0 is coming along :-D But, is version 1.x going to be updated to support Ember >= 2.15? |
@Ramblurr, upgrading 1.x means that some partials (IDK all partials or only a part of them) should be combined into one template. |
Good to hear! I didn't realize this was caused by a bug in Ember rather than a deprecation/change. Thanks @onechiporenko |
v2.0.0-alpha.1 is released. It's a pre-release for anyone who wants to test new design and help to improve it. Run |
Hey, first of all thanks for a great addon! When using Ember 2.15 with Keep up the good work! |
@DennisNygren, main idea for version 2.* is replace templates (partials) with contextual and "normal" components. So, upgrade to version 2.* requires refactoring. Some migration docs will be prepared later. For now - just replace partials with components. |
|
@onechiporenko Ok thanks for your quick reply! |
Great work so far! Is there a particular reason not to pass That used to be the case before and I relied on it (on accessing |
@arnebit, Passing |
|
Separated issue is created =========== |
@onechiporenko Why is passing The aforementioned
|
Check new demo page for v.2 http://onechiporenko.github.io/ember-models-table/v.2/ |
|
I am using ember-model-table 2.0beta after the issue came up with "partials" in ember 2.15.I want to know if there is an option to customize the pagination in 2.0 such as "componentFooterTemplate" in 1.0? Pls help as it affects my app in production. |
@SakuDivya, sure. You may override models-table/footer or use block content like: {{#models-table data=data columns=columns as |mt|}}
{{#mt.footer as |footer|}}
{{! custom markup here }}
{{/mt.footer}}
{{/models-table}} |
Thanks for the quick reply. But if want pagination functionalities and only need to change the UI lookup of page numbers,what needs to be done.Do i have to write a separate component and write all functionalities instead of {{footer.pagination-numeric}} ? |
@SakuDivya, pls create a separated issue. This one is like a "news-board" for 2.x. |
I have created.Pls take a look Thank u... |
Looking really good, thanks for all the hard work @onechiporenko ! |
|
models-table
to use contextual componentsember-cli-mirage
andember-cli-page-object
)server-paginated
table too)The text was updated successfully, but these errors were encountered: