Yuvaraja Balamurugan
Yuvaraja Balamurugan
Any updates on this? I am facing a similar issue!!
@luismiv85 In both the AMS serialization, I believe you should do a `.as_json` at the end else this would just instantiate the object and obviously be faster.
@gburtini Did yarn actually lock your package versions? We ourself are considering to move to yarn from npm because of the lock file issue. Is there anything else to consider...
@bf4 Yes the namespace is not respected even though the render is called from a `V1` namespaced controller. I tried specifying `namespace` but it's the same. But, I've been bypassing...
@bf4 You mean the fix in AMS itself? No, not yet. I can try it out and make a PR with tests over the weekend.
@bf4 Yes, it's partly related. When the `namespace` is explicitly specified like so, ``` class ResourceNamespace class PostSerializer < ActiveModel::Serializer has_many :comments, namespace: ResourceNamespace end class CommentSerializer < ActiveModel::Serializer; end...
I can confirm that when disabling `sticky-element`, the scroll works correctly. Also looks like maybe https://github.com/kaliber5/ember-sticky-element/issues/38 is the reason? I say maybe because I am not familiar with the `ember-sticky`...
@MelSumner What would the designs look like for this?
I get your point, but if there are 10 keybindings, all of them would have a guard condition to reject if the preview is active. Or one more alternative could...
@jabbermarky I thought so too and did remove the use of id. The issue was still happening. I did not have enough time to get to the bottom of it....