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

Support for custom @tagName #74

Closed
Panman82 opened this issue May 29, 2019 · 5 comments
Closed

Support for custom @tagName #74

Panman82 opened this issue May 29, 2019 · 5 comments
Milestone

Comments

@Panman82
Copy link
Contributor

Panman82 commented May 29, 2019

With the move to Glimmer Components, the Ember Component tagName property/option does not apply. There is a Dynamic tag names RFC that has been accepted but not implemented yet. Additionally, I'd like to wait for the Add new basic helpers to Ember RFC to land so that we can keep <FroalaContent /> as a template-only component. Eg: {{#let (element (or @tagName "div") as |Tag|}}

@Panman82
Copy link
Contributor Author

Forgot to mention, the (or @tagName "div") could instead be (if @tagName @tagName "div"), inline if, so the basic helpers RFC isn't needed necessarily.

@Panman82 Panman82 added this to the 3.0 milestone Nov 16, 2019
@Panman82 Panman82 changed the title Support for custom tagName Support for custom @tagName Nov 22, 2019
@Panman82
Copy link
Contributor Author

FWIW, could use ember-element-helper but blocked on an issue with modifiers.

@Panman82
Copy link
Contributor Author

Looks like we'll have to reduce back-compat (currently 3.4+) to get @tagName support due to a glimmer-vm issue with modifiers prior to ember 3.7.2 (see the "issues with modifiers" link above).

@Panman82
Copy link
Contributor Author

So there has been zero movement on this from the Ember front. There are three options we can take with this addon;

  1. Continue to wait for the built-in {{element}} helper and polyfill
  2. Use the ember-element-helper addon and reduce backwards compat to 3.7.2+
  3. Drop the idea of supporting @tagName since the <div> variant is probably the best option for ember.js

Taking votes or other ideas. 😄

@Panman82
Copy link
Contributor Author

At this point we'll go with option 3 of not supporting a custom @tagName since there still is no movement here on the ember front, and additionally the ember-element-helper addon outputs a custom Ember Component instead of a Glimmer Component (which negates any perf improvements). Will close for now but post here if you need support and we can discuss again. Thanks

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

1 participant