Ghost/ghost/admin/app/components/members-activity/no-events.hbs

<div class="no-posts-box">
    <div class="no-posts">
        {{svg-jar "activity-placeholder" class="gh-members-placeholder"}}
        {{#if @filter}}
            <h4>No activities match the current filter</h4>
            <LinkTo @route="members-activity" @query={{reset-query-params "members-activity"}} class="gh-btn gh-btn-lg">
                <span>Show all activity</span>
            </LinkTo>
        {{else}}
            <h4>No member activity yet</h4>
        {{/if}}
    </div>
</div>
Added fetching of member events to members-activity screen refs https://github.com/TryGhost/Team/issues/1277 - added `ember-could-get-used-to-this` dependency to get access to Resources - context: https://www.pzuraq.com/introducing-use/ - added MembersEventFetcher resource for loading members events - using a Resource allows for a better data loading experience using only components - uses raw data from the API rather than going through Ember Data because we don't need full models or session-length caching that gives us - data is kept around in memory for the lifecycle of the resource, if the `filter` param changes the resource is torn down and recreated so it starts from page 1 again, once it's no longer used by a component it's torn down so data isn't kept around - paginates by using a `created_at:<={lastSeenTimestamp}` filter - this assumes the API can handle that effectively as a cursor with no duplicate or skipped records - updated `members-activity` template to use the new resource and control data loading using infinite scroll - moved overall screen structure from the `<MembersActivity::Table>` component into the `members-activity` template so that the table component can stay focused on just the table display 2022-01-22 18:35:08 +03:00			`<div class="no-posts-box">`
			`<div class="no-posts">`
Updated activity feed empty state icon 2022-07-12 16:03:40 +03:00			`{{svg-jar "activity-placeholder" class="gh-members-placeholder"}}`
Added fetching of member events to members-activity screen refs https://github.com/TryGhost/Team/issues/1277 - added `ember-could-get-used-to-this` dependency to get access to Resources - context: https://www.pzuraq.com/introducing-use/ - added MembersEventFetcher resource for loading members events - using a Resource allows for a better data loading experience using only components - uses raw data from the API rather than going through Ember Data because we don't need full models or session-length caching that gives us - data is kept around in memory for the lifecycle of the resource, if the `filter` param changes the resource is torn down and recreated so it starts from page 1 again, once it's no longer used by a component it's torn down so data isn't kept around - paginates by using a `created_at:<={lastSeenTimestamp}` filter - this assumes the API can handle that effectively as a cursor with no duplicate or skipped records - updated `members-activity` template to use the new resource and control data loading using infinite scroll - moved overall screen structure from the `<MembersActivity::Table>` component into the `members-activity` template so that the table component can stay focused on just the table display 2022-01-22 18:35:08 +03:00			`{{#if @filter}}`
Fixed empty states spacing regression 2022-06-02 00:31:23 +03:00			`<h4>No activities match the current filter</h4>`
Added member details and hid member column on activity feed when filtered by member refs https://github.com/TryGhost/Team/issues/1277 - extracted member details display into a `<GhMemberDetails>` component for re-use in the member details and members-activity screens - added loading of member record from the member id query param and displayed the member details above the table when a member filter is present - hid the member column in the events table when a member filter is present - it's useless/repeated info at that point 2022-01-25 19:34:18 +03:00			`<LinkTo @route="members-activity" @query={{reset-query-params "members-activity"}} class="gh-btn gh-btn-lg">`
Added fetching of member events to members-activity screen refs https://github.com/TryGhost/Team/issues/1277 - added `ember-could-get-used-to-this` dependency to get access to Resources - context: https://www.pzuraq.com/introducing-use/ - added MembersEventFetcher resource for loading members events - using a Resource allows for a better data loading experience using only components - uses raw data from the API rather than going through Ember Data because we don't need full models or session-length caching that gives us - data is kept around in memory for the lifecycle of the resource, if the `filter` param changes the resource is torn down and recreated so it starts from page 1 again, once it's no longer used by a component it's torn down so data isn't kept around - paginates by using a `created_at:<={lastSeenTimestamp}` filter - this assumes the API can handle that effectively as a cursor with no duplicate or skipped records - updated `members-activity` template to use the new resource and control data loading using infinite scroll - moved overall screen structure from the `<MembersActivity::Table>` component into the `members-activity` template so that the table component can stay focused on just the table display 2022-01-22 18:35:08 +03:00			`<span>Show all activity</span>`
			`</LinkTo>`
			`{{else}}`
Updated activity feed empty state icon 2022-07-12 16:03:40 +03:00			`<h4>No member activity yet</h4>`
Added fetching of member events to members-activity screen refs https://github.com/TryGhost/Team/issues/1277 - added `ember-could-get-used-to-this` dependency to get access to Resources - context: https://www.pzuraq.com/introducing-use/ - added MembersEventFetcher resource for loading members events - using a Resource allows for a better data loading experience using only components - uses raw data from the API rather than going through Ember Data because we don't need full models or session-length caching that gives us - data is kept around in memory for the lifecycle of the resource, if the `filter` param changes the resource is torn down and recreated so it starts from page 1 again, once it's no longer used by a component it's torn down so data isn't kept around - paginates by using a `created_at:<={lastSeenTimestamp}` filter - this assumes the API can handle that effectively as a cursor with no duplicate or skipped records - updated `members-activity` template to use the new resource and control data loading using infinite scroll - moved overall screen structure from the `<MembersActivity::Table>` component into the `members-activity` template so that the table component can stay focused on just the table display 2022-01-22 18:35:08 +03:00			`{{/if}}`
			`</div>`
			`</div>`