Databases
StackOverflow2013
Postsdbo
PORails + Ember.js + Devise freelance journalist app - data scoping
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails + Ember.js + Devise freelance journalist app - data scoping
    primarykey
    data
    text
    <p>Apologies, I have been in ember.js-land for so long, I'm fumbling Rails + active_model_serializers JSON api basics. </p> <p>So let's say I'm a freelance journalist and am building an app where a writer can publish Articles to different Company-specific sites through a single user account. </p> <pre><code>Rails Relationships User has_many :company_memberships User has_many :companies, :through =&gt; :company_memberships Company has_many :company_memberships Company_membership belongs_to :user Company_membership belongs_to :company Article belongs_to :company_membership Article has_many :comments Comment belongs_to :article </code></pre> <p>I am using Rails 3+, Devise, Active_Model_Serializers, Ember-Data and Ember.js. </p> <p>I want to set up a flow where the user comes to the site, logs in (very easy using devise) and is redirected to a rails page where he can select which Company's dashboard he wants to go to (by just clicking on a link). </p> <p>Now comes the tricky part. When he clicks on a specific company's link, he should be directed to a Rails view that contains an ember app whose serialization scope is set to the current_company_membership or current_company and not just the current_user.</p> <p>How do I create a rails or active_model_serializers method that scopes data to just the current_company as dictated by current_company_membership, and then passes along this data to the ember app?</p> <hr> <p>Also, as a bonus, I need the name and email address of the current_user - how do I pass this information along to the ember app as well? I have seen <a href="http://say26.com/using-rails-devise-with-ember-js" rel="nofollow">this dude's</a> article, but have not been able to get it working when trying to scope data through just company_membership and not current_user. </p> <p>Any help would be awesome! I'll add more detail and code if need be, but I have a feeling I'm forgetting something pretty simple here. </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJack Johnson
    1. USJack Johnson
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORails + Ember.js + Devise freelance journalist app - data scoping
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORails + Ember.js + Devise freelance journalist app - data scoping
      1. This table or related slice is empty.
      1. VTDownMod
    3. VO
      singulars
      1. PORails + Ember.js + Devise freelance journalist app - data scoping
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'll try to answer in a bit. Your question is a bit on the lengthy side btw... A more reduced example would have been nice. I like to use Blog/Article/Comment as my canonical example app, so people don't have to get acquainted with my application domain.
      singulars
      1. PORails + Ember.js + Devise freelance journalist app - data scoping
      1. USJo Liss
    2. CO@JoLiss sorry about that, I was using this as an example app idea to try and conceptualize something I couldn't quite grasp at the moment. I still falter sometimes when trying to figure out what should be handled completely client-side and what should be handled either on the server or in a plain ol' rails view. Thanks for your response!
      singulars
      1. PORails + Ember.js + Devise freelance journalist app - data scoping
      1. USJack Johnson
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload