2017-05-02 20:04:16 -04:00
|
|
|
import React from 'react';
|
2017-02-17 20:37:59 -05:00
|
|
|
import { connect } from 'react-redux';
|
2017-04-21 14:05:35 -04:00
|
|
|
import PropTypes from 'prop-types';
|
2017-02-17 20:37:59 -05:00
|
|
|
import ImmutablePropTypes from 'react-immutable-proptypes';
|
|
|
|
import { fetchStatus } from '../../actions/statuses';
|
2017-02-26 17:06:27 -05:00
|
|
|
import MissingIndicator from '../../components/missing_indicator';
|
2017-02-17 20:37:59 -05:00
|
|
|
import DetailedStatus from './components/detailed_status';
|
|
|
|
import ActionBar from './components/action_bar';
|
|
|
|
import Column from '../ui/components/column';
|
|
|
|
import {
|
|
|
|
favourite,
|
|
|
|
unfavourite,
|
|
|
|
reblog,
|
2017-05-20 11:31:47 -04:00
|
|
|
unreblog,
|
2017-08-24 19:41:18 -04:00
|
|
|
pin,
|
|
|
|
unpin,
|
2017-02-17 20:37:59 -05:00
|
|
|
} from '../../actions/interactions';
|
2016-10-24 11:11:02 -04:00
|
|
|
import {
|
|
|
|
replyCompose,
|
2017-05-20 11:31:47 -04:00
|
|
|
mentionCompose,
|
2017-02-17 20:37:59 -05:00
|
|
|
} from '../../actions/compose';
|
|
|
|
import { deleteStatus } from '../../actions/statuses';
|
2017-02-14 14:59:26 -05:00
|
|
|
import { initReport } from '../../actions/reports';
|
2017-06-23 10:05:04 -04:00
|
|
|
import { makeGetStatus } from '../../selectors';
|
2017-02-17 20:37:59 -05:00
|
|
|
import { ScrollContainer } from 'react-router-scroll';
|
|
|
|
import ColumnBackButton from '../../components/column_back_button';
|
|
|
|
import StatusContainer from '../../containers/status_container';
|
2017-04-01 16:11:28 -04:00
|
|
|
import { openModal } from '../../actions/modal';
|
2017-06-23 10:05:04 -04:00
|
|
|
import { defineMessages, injectIntl } from 'react-intl';
|
2017-05-02 20:04:16 -04:00
|
|
|
import ImmutablePureComponent from 'react-immutable-pure-component';
|
2017-04-22 22:39:50 -04:00
|
|
|
|
|
|
|
const messages = defineMessages({
|
|
|
|
deleteConfirm: { id: 'confirmations.delete.confirm', defaultMessage: 'Delete' },
|
2017-05-20 11:31:47 -04:00
|
|
|
deleteMessage: { id: 'confirmations.delete.message', defaultMessage: 'Are you sure you want to delete this status?' },
|
2017-04-22 22:39:50 -04:00
|
|
|
});
|
2016-09-15 18:21:51 -04:00
|
|
|
|
2016-10-24 11:11:02 -04:00
|
|
|
const makeMapStateToProps = () => {
|
|
|
|
const getStatus = makeGetStatus();
|
|
|
|
|
|
|
|
const mapStateToProps = (state, props) => ({
|
Change IDs to strings rather than numbers in API JSON output (#5019)
* Fix JavaScript interface with long IDs
Somewhat predictably, the JS interface handled IDs as numbers, which in
JS are IEEE double-precision floats. This loses some precision when
working with numbers as large as those generated by the new ID scheme,
so we instead handle them here as strings. This is relatively simple,
and doesn't appear to have caused any problems, but should definitely
be tested more thoroughly than the built-in tests. Several days of use
appear to support this working properly.
BREAKING CHANGE:
The major(!) change here is that IDs are now returned as strings by the
REST endpoints, rather than as integers. In practice, relatively few
changes were required to make the existing JS UI work with this change,
but it will likely hit API clients pretty hard: it's an entirely
different type to consume. (The one API client I tested, Tusky, handles
this with no problems, however.)
Twitter ran into this issue when introducing Snowflake IDs, and decided
to instead introduce an `id_str` field in JSON responses. I have opted
to *not* do that, and instead force all IDs to 64-bit integers
represented by strings in one go. (I believe Twitter exacerbated their
problem by rolling out the changes three times: once for statuses, once
for DMs, and once for user IDs, as well as by leaving an integer ID
value in JSON. As they said, "If you’re using the `id` field with JSON
in a Javascript-related language, there is a very high likelihood that
the integers will be silently munged by Javascript interpreters. In most
cases, this will result in behavior such as being unable to load or
delete a specific direct message, because the ID you're sending to the
API is different than the actual identifier associated with the
message." [1]) However, given that this is a significant change for API
users, alternatives or a transition time may be appropriate.
1: https://blog.twitter.com/developer/en_us/a/2011/direct-messages-going-snowflake-on-sep-30-2011.html
* Additional fixes for stringified IDs in JSON
These should be the last two. These were identified using eslint to try
to identify any plain casts to JavaScript numbers. (Some such casts are
legitimate, but these were not.)
Adding the following to .eslintrc.yml will identify casts to numbers:
~~~
no-restricted-syntax:
- warn
- selector: UnaryExpression[operator='+'] > :not(Literal)
message: Avoid the use of unary +
- selector: CallExpression[callee.name='Number']
message: Casting with Number() may coerce string IDs to numbers
~~~
The remaining three casts appear legitimate: two casts to array indices,
one in a server to turn an environment variable into a number.
* Back out RelationshipsController Change
This was made to make a test a bit less flakey, but has nothing to
do with this branch.
* Change internal streaming payloads to stringified IDs as well
Per
https://github.com/tootsuite/mastodon/pull/5019#issuecomment-330736452
we need these changes to send deleted status IDs as strings, not
integers.
2017-09-20 08:53:48 -04:00
|
|
|
status: getStatus(state, props.params.statusId),
|
|
|
|
ancestorsIds: state.getIn(['contexts', 'ancestors', props.params.statusId]),
|
|
|
|
descendantsIds: state.getIn(['contexts', 'descendants', props.params.statusId]),
|
2017-04-11 10:10:16 -04:00
|
|
|
me: state.getIn(['meta', 'me']),
|
2017-04-17 06:14:03 -04:00
|
|
|
boostModal: state.getIn(['meta', 'boost_modal']),
|
2017-05-29 11:56:13 -04:00
|
|
|
deleteModal: state.getIn(['meta', 'delete_modal']),
|
2017-05-20 11:31:47 -04:00
|
|
|
autoPlayGif: state.getIn(['meta', 'auto_play_gif']),
|
2016-10-24 11:11:02 -04:00
|
|
|
});
|
|
|
|
|
|
|
|
return mapStateToProps;
|
|
|
|
};
|
2016-09-15 18:21:51 -04:00
|
|
|
|
2017-06-23 13:36:54 -04:00
|
|
|
@injectIntl
|
|
|
|
@connect(makeMapStateToProps)
|
|
|
|
export default class Status extends ImmutablePureComponent {
|
2017-04-21 14:05:35 -04:00
|
|
|
|
2017-05-12 08:44:10 -04:00
|
|
|
static contextTypes = {
|
2017-05-20 11:31:47 -04:00
|
|
|
router: PropTypes.object,
|
2017-05-12 08:44:10 -04:00
|
|
|
};
|
|
|
|
|
|
|
|
static propTypes = {
|
|
|
|
params: PropTypes.object.isRequired,
|
|
|
|
dispatch: PropTypes.func.isRequired,
|
|
|
|
status: ImmutablePropTypes.map,
|
|
|
|
ancestorsIds: ImmutablePropTypes.list,
|
|
|
|
descendantsIds: ImmutablePropTypes.list,
|
Change IDs to strings rather than numbers in API JSON output (#5019)
* Fix JavaScript interface with long IDs
Somewhat predictably, the JS interface handled IDs as numbers, which in
JS are IEEE double-precision floats. This loses some precision when
working with numbers as large as those generated by the new ID scheme,
so we instead handle them here as strings. This is relatively simple,
and doesn't appear to have caused any problems, but should definitely
be tested more thoroughly than the built-in tests. Several days of use
appear to support this working properly.
BREAKING CHANGE:
The major(!) change here is that IDs are now returned as strings by the
REST endpoints, rather than as integers. In practice, relatively few
changes were required to make the existing JS UI work with this change,
but it will likely hit API clients pretty hard: it's an entirely
different type to consume. (The one API client I tested, Tusky, handles
this with no problems, however.)
Twitter ran into this issue when introducing Snowflake IDs, and decided
to instead introduce an `id_str` field in JSON responses. I have opted
to *not* do that, and instead force all IDs to 64-bit integers
represented by strings in one go. (I believe Twitter exacerbated their
problem by rolling out the changes three times: once for statuses, once
for DMs, and once for user IDs, as well as by leaving an integer ID
value in JSON. As they said, "If you’re using the `id` field with JSON
in a Javascript-related language, there is a very high likelihood that
the integers will be silently munged by Javascript interpreters. In most
cases, this will result in behavior such as being unable to load or
delete a specific direct message, because the ID you're sending to the
API is different than the actual identifier associated with the
message." [1]) However, given that this is a significant change for API
users, alternatives or a transition time may be appropriate.
1: https://blog.twitter.com/developer/en_us/a/2011/direct-messages-going-snowflake-on-sep-30-2011.html
* Additional fixes for stringified IDs in JSON
These should be the last two. These were identified using eslint to try
to identify any plain casts to JavaScript numbers. (Some such casts are
legitimate, but these were not.)
Adding the following to .eslintrc.yml will identify casts to numbers:
~~~
no-restricted-syntax:
- warn
- selector: UnaryExpression[operator='+'] > :not(Literal)
message: Avoid the use of unary +
- selector: CallExpression[callee.name='Number']
message: Casting with Number() may coerce string IDs to numbers
~~~
The remaining three casts appear legitimate: two casts to array indices,
one in a server to turn an environment variable into a number.
* Back out RelationshipsController Change
This was made to make a test a bit less flakey, but has nothing to
do with this branch.
* Change internal streaming payloads to stringified IDs as well
Per
https://github.com/tootsuite/mastodon/pull/5019#issuecomment-330736452
we need these changes to send deleted status IDs as strings, not
integers.
2017-09-20 08:53:48 -04:00
|
|
|
me: PropTypes.string,
|
2017-05-12 08:44:10 -04:00
|
|
|
boostModal: PropTypes.bool,
|
2017-05-29 11:56:13 -04:00
|
|
|
deleteModal: PropTypes.bool,
|
2017-05-12 08:44:10 -04:00
|
|
|
autoPlayGif: PropTypes.bool,
|
2017-05-20 11:31:47 -04:00
|
|
|
intl: PropTypes.object.isRequired,
|
2017-05-12 08:44:10 -04:00
|
|
|
};
|
2016-09-15 18:21:51 -04:00
|
|
|
|
|
|
|
componentWillMount () {
|
Change IDs to strings rather than numbers in API JSON output (#5019)
* Fix JavaScript interface with long IDs
Somewhat predictably, the JS interface handled IDs as numbers, which in
JS are IEEE double-precision floats. This loses some precision when
working with numbers as large as those generated by the new ID scheme,
so we instead handle them here as strings. This is relatively simple,
and doesn't appear to have caused any problems, but should definitely
be tested more thoroughly than the built-in tests. Several days of use
appear to support this working properly.
BREAKING CHANGE:
The major(!) change here is that IDs are now returned as strings by the
REST endpoints, rather than as integers. In practice, relatively few
changes were required to make the existing JS UI work with this change,
but it will likely hit API clients pretty hard: it's an entirely
different type to consume. (The one API client I tested, Tusky, handles
this with no problems, however.)
Twitter ran into this issue when introducing Snowflake IDs, and decided
to instead introduce an `id_str` field in JSON responses. I have opted
to *not* do that, and instead force all IDs to 64-bit integers
represented by strings in one go. (I believe Twitter exacerbated their
problem by rolling out the changes three times: once for statuses, once
for DMs, and once for user IDs, as well as by leaving an integer ID
value in JSON. As they said, "If you’re using the `id` field with JSON
in a Javascript-related language, there is a very high likelihood that
the integers will be silently munged by Javascript interpreters. In most
cases, this will result in behavior such as being unable to load or
delete a specific direct message, because the ID you're sending to the
API is different than the actual identifier associated with the
message." [1]) However, given that this is a significant change for API
users, alternatives or a transition time may be appropriate.
1: https://blog.twitter.com/developer/en_us/a/2011/direct-messages-going-snowflake-on-sep-30-2011.html
* Additional fixes for stringified IDs in JSON
These should be the last two. These were identified using eslint to try
to identify any plain casts to JavaScript numbers. (Some such casts are
legitimate, but these were not.)
Adding the following to .eslintrc.yml will identify casts to numbers:
~~~
no-restricted-syntax:
- warn
- selector: UnaryExpression[operator='+'] > :not(Literal)
message: Avoid the use of unary +
- selector: CallExpression[callee.name='Number']
message: Casting with Number() may coerce string IDs to numbers
~~~
The remaining three casts appear legitimate: two casts to array indices,
one in a server to turn an environment variable into a number.
* Back out RelationshipsController Change
This was made to make a test a bit less flakey, but has nothing to
do with this branch.
* Change internal streaming payloads to stringified IDs as well
Per
https://github.com/tootsuite/mastodon/pull/5019#issuecomment-330736452
we need these changes to send deleted status IDs as strings, not
integers.
2017-09-20 08:53:48 -04:00
|
|
|
this.props.dispatch(fetchStatus(this.props.params.statusId));
|
2017-04-21 14:05:35 -04:00
|
|
|
}
|
2016-09-15 18:21:51 -04:00
|
|
|
|
|
|
|
componentWillReceiveProps (nextProps) {
|
|
|
|
if (nextProps.params.statusId !== this.props.params.statusId && nextProps.params.statusId) {
|
Change IDs to strings rather than numbers in API JSON output (#5019)
* Fix JavaScript interface with long IDs
Somewhat predictably, the JS interface handled IDs as numbers, which in
JS are IEEE double-precision floats. This loses some precision when
working with numbers as large as those generated by the new ID scheme,
so we instead handle them here as strings. This is relatively simple,
and doesn't appear to have caused any problems, but should definitely
be tested more thoroughly than the built-in tests. Several days of use
appear to support this working properly.
BREAKING CHANGE:
The major(!) change here is that IDs are now returned as strings by the
REST endpoints, rather than as integers. In practice, relatively few
changes were required to make the existing JS UI work with this change,
but it will likely hit API clients pretty hard: it's an entirely
different type to consume. (The one API client I tested, Tusky, handles
this with no problems, however.)
Twitter ran into this issue when introducing Snowflake IDs, and decided
to instead introduce an `id_str` field in JSON responses. I have opted
to *not* do that, and instead force all IDs to 64-bit integers
represented by strings in one go. (I believe Twitter exacerbated their
problem by rolling out the changes three times: once for statuses, once
for DMs, and once for user IDs, as well as by leaving an integer ID
value in JSON. As they said, "If you’re using the `id` field with JSON
in a Javascript-related language, there is a very high likelihood that
the integers will be silently munged by Javascript interpreters. In most
cases, this will result in behavior such as being unable to load or
delete a specific direct message, because the ID you're sending to the
API is different than the actual identifier associated with the
message." [1]) However, given that this is a significant change for API
users, alternatives or a transition time may be appropriate.
1: https://blog.twitter.com/developer/en_us/a/2011/direct-messages-going-snowflake-on-sep-30-2011.html
* Additional fixes for stringified IDs in JSON
These should be the last two. These were identified using eslint to try
to identify any plain casts to JavaScript numbers. (Some such casts are
legitimate, but these were not.)
Adding the following to .eslintrc.yml will identify casts to numbers:
~~~
no-restricted-syntax:
- warn
- selector: UnaryExpression[operator='+'] > :not(Literal)
message: Avoid the use of unary +
- selector: CallExpression[callee.name='Number']
message: Casting with Number() may coerce string IDs to numbers
~~~
The remaining three casts appear legitimate: two casts to array indices,
one in a server to turn an environment variable into a number.
* Back out RelationshipsController Change
This was made to make a test a bit less flakey, but has nothing to
do with this branch.
* Change internal streaming payloads to stringified IDs as well
Per
https://github.com/tootsuite/mastodon/pull/5019#issuecomment-330736452
we need these changes to send deleted status IDs as strings, not
integers.
2017-09-20 08:53:48 -04:00
|
|
|
this.props.dispatch(fetchStatus(nextProps.params.statusId));
|
2016-09-15 18:21:51 -04:00
|
|
|
}
|
2017-04-21 14:05:35 -04:00
|
|
|
}
|
2016-09-15 18:21:51 -04:00
|
|
|
|
2017-05-12 08:44:10 -04:00
|
|
|
handleFavouriteClick = (status) => {
|
2017-02-16 20:33:10 -05:00
|
|
|
if (status.get('favourited')) {
|
|
|
|
this.props.dispatch(unfavourite(status));
|
|
|
|
} else {
|
|
|
|
this.props.dispatch(favourite(status));
|
|
|
|
}
|
2017-04-21 14:05:35 -04:00
|
|
|
}
|
2016-09-17 11:47:26 -04:00
|
|
|
|
2017-08-24 19:41:18 -04:00
|
|
|
handlePin = (status) => {
|
|
|
|
if (status.get('pinned')) {
|
|
|
|
this.props.dispatch(unpin(status));
|
|
|
|
} else {
|
|
|
|
this.props.dispatch(pin(status));
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2017-05-12 08:44:10 -04:00
|
|
|
handleReplyClick = (status) => {
|
2017-06-20 14:40:03 -04:00
|
|
|
this.props.dispatch(replyCompose(status, this.context.router.history));
|
2017-04-21 14:05:35 -04:00
|
|
|
}
|
2016-09-17 11:47:26 -04:00
|
|
|
|
2017-05-12 08:44:10 -04:00
|
|
|
handleModalReblog = (status) => {
|
2017-04-10 22:28:52 -04:00
|
|
|
this.props.dispatch(reblog(status));
|
2017-04-21 14:05:35 -04:00
|
|
|
}
|
2017-04-10 22:28:52 -04:00
|
|
|
|
2017-05-12 08:44:10 -04:00
|
|
|
handleReblogClick = (status, e) => {
|
2017-02-16 20:33:10 -05:00
|
|
|
if (status.get('reblogged')) {
|
|
|
|
this.props.dispatch(unreblog(status));
|
|
|
|
} else {
|
2017-04-12 20:15:45 -04:00
|
|
|
if (e.shiftKey || !this.props.boostModal) {
|
2017-04-11 08:34:14 -04:00
|
|
|
this.handleModalReblog(status);
|
|
|
|
} else {
|
|
|
|
this.props.dispatch(openModal('BOOST', { status, onReblog: this.handleModalReblog }));
|
|
|
|
}
|
2017-02-16 20:33:10 -05:00
|
|
|
}
|
2017-04-21 14:05:35 -04:00
|
|
|
}
|
2016-09-17 11:47:26 -04:00
|
|
|
|
2017-05-12 08:44:10 -04:00
|
|
|
handleDeleteClick = (status) => {
|
2017-04-22 22:39:50 -04:00
|
|
|
const { dispatch, intl } = this.props;
|
|
|
|
|
2017-05-29 11:56:13 -04:00
|
|
|
if (!this.props.deleteModal) {
|
|
|
|
dispatch(deleteStatus(status.get('id')));
|
|
|
|
} else {
|
|
|
|
dispatch(openModal('CONFIRM', {
|
|
|
|
message: intl.formatMessage(messages.deleteMessage),
|
|
|
|
confirm: intl.formatMessage(messages.deleteConfirm),
|
|
|
|
onConfirm: () => dispatch(deleteStatus(status.get('id'))),
|
|
|
|
}));
|
|
|
|
}
|
2017-04-21 14:05:35 -04:00
|
|
|
}
|
2016-10-09 16:19:15 -04:00
|
|
|
|
2017-05-12 08:44:10 -04:00
|
|
|
handleMentionClick = (account, router) => {
|
2017-01-30 15:40:55 -05:00
|
|
|
this.props.dispatch(mentionCompose(account, router));
|
2017-04-21 14:05:35 -04:00
|
|
|
}
|
2016-10-24 11:11:02 -04:00
|
|
|
|
2017-05-12 08:44:10 -04:00
|
|
|
handleOpenMedia = (media, index) => {
|
2017-04-01 16:11:28 -04:00
|
|
|
this.props.dispatch(openModal('MEDIA', { media, index }));
|
2017-04-21 14:05:35 -04:00
|
|
|
}
|
2016-10-24 12:07:40 -04:00
|
|
|
|
2017-05-12 08:44:10 -04:00
|
|
|
handleOpenVideo = (media, time) => {
|
2017-04-13 11:01:09 -04:00
|
|
|
this.props.dispatch(openModal('VIDEO', { media, time }));
|
2017-04-21 14:05:35 -04:00
|
|
|
}
|
2017-04-13 09:04:18 -04:00
|
|
|
|
2017-05-12 08:44:10 -04:00
|
|
|
handleReport = (status) => {
|
2017-02-14 14:59:26 -05:00
|
|
|
this.props.dispatch(initReport(status.get('account'), status));
|
2017-04-21 14:05:35 -04:00
|
|
|
}
|
2017-02-14 14:59:26 -05:00
|
|
|
|
2017-08-30 21:38:35 -04:00
|
|
|
handleEmbed = (status) => {
|
|
|
|
this.props.dispatch(openModal('EMBED', { url: status.get('url') }));
|
|
|
|
}
|
|
|
|
|
2016-09-15 18:21:51 -04:00
|
|
|
renderChildren (list) {
|
2016-10-24 11:11:02 -04:00
|
|
|
return list.map(id => <StatusContainer key={id} id={id} />);
|
2017-04-21 14:05:35 -04:00
|
|
|
}
|
2016-09-15 18:21:51 -04:00
|
|
|
|
|
|
|
render () {
|
2016-10-24 11:11:02 -04:00
|
|
|
let ancestors, descendants;
|
2017-04-17 06:14:03 -04:00
|
|
|
const { status, ancestorsIds, descendantsIds, me, autoPlayGif } = this.props;
|
2016-09-15 18:21:51 -04:00
|
|
|
|
|
|
|
if (status === null) {
|
2016-10-07 10:00:11 -04:00
|
|
|
return (
|
|
|
|
<Column>
|
2017-02-19 02:32:35 -05:00
|
|
|
<ColumnBackButton />
|
2017-02-26 17:06:27 -05:00
|
|
|
<MissingIndicator />
|
2016-10-07 10:00:11 -04:00
|
|
|
</Column>
|
|
|
|
);
|
2016-09-15 18:21:51 -04:00
|
|
|
}
|
|
|
|
|
2016-10-30 10:06:43 -04:00
|
|
|
if (ancestorsIds && ancestorsIds.size > 0) {
|
2016-10-24 11:11:02 -04:00
|
|
|
ancestors = <div>{this.renderChildren(ancestorsIds)}</div>;
|
|
|
|
}
|
|
|
|
|
2016-10-30 10:06:43 -04:00
|
|
|
if (descendantsIds && descendantsIds.size > 0) {
|
2016-10-24 11:11:02 -04:00
|
|
|
descendants = <div>{this.renderChildren(descendantsIds)}</div>;
|
|
|
|
}
|
|
|
|
|
2016-09-15 18:21:51 -04:00
|
|
|
return (
|
2016-10-07 10:00:11 -04:00
|
|
|
<Column>
|
2016-10-19 12:20:19 -04:00
|
|
|
<ColumnBackButton />
|
2016-09-18 07:03:37 -04:00
|
|
|
|
2016-10-19 12:20:19 -04:00
|
|
|
<ScrollContainer scrollKey='thread'>
|
2017-04-22 22:26:55 -04:00
|
|
|
<div className='scrollable detailed-status__wrapper'>
|
2016-10-24 11:11:02 -04:00
|
|
|
{ancestors}
|
2016-09-18 07:03:37 -04:00
|
|
|
|
Feature conversations muting (#3017)
* Add <ostatus:conversation /> tag to Atom input/output
Only uses ref attribute (not href) because href would be
the alternate link that's always included also.
Creates new conversation for every non-reply status. Carries
over conversation for every reply. Keeps remote URIs verbatim,
generates local URIs on the fly like the rest of them.
* Conversation muting - prevents notifications that reference a conversation
(including replies, favourites, reblogs) from being created. API endpoints
/api/v1/statuses/:id/mute and /api/v1/statuses/:id/unmute
Currently no way to tell when a status/conversation is muted, so the web UI
only has a "disable notifications" button, doesn't work as a toggle
* Display "Dismiss notifications" on all statuses in notifications column, not just own
* Add "muted" as a boolean attribute on statuses JSON
For now always false on contained reblogs, since it's only relevant for
statuses returned from the notifications endpoint, which are not nested
Remove "Disable notifications" from detailed status view, since it's
only relevant in the notifications column
* Up max class length
* Remove pending test for conversation mute
* Add tests, clean up
* Rename to "mute conversation" and "unmute conversation"
* Raise validation error when trying to mute/unmute status without conversation
2017-05-14 21:04:13 -04:00
|
|
|
<DetailedStatus
|
|
|
|
status={status}
|
|
|
|
autoPlayGif={autoPlayGif}
|
|
|
|
me={me}
|
|
|
|
onOpenVideo={this.handleOpenVideo}
|
|
|
|
onOpenMedia={this.handleOpenMedia}
|
|
|
|
/>
|
|
|
|
|
|
|
|
<ActionBar
|
|
|
|
status={status}
|
|
|
|
me={me}
|
|
|
|
onReply={this.handleReplyClick}
|
|
|
|
onFavourite={this.handleFavouriteClick}
|
|
|
|
onReblog={this.handleReblogClick}
|
|
|
|
onDelete={this.handleDeleteClick}
|
|
|
|
onMention={this.handleMentionClick}
|
|
|
|
onReport={this.handleReport}
|
2017-08-24 19:41:18 -04:00
|
|
|
onPin={this.handlePin}
|
2017-08-30 21:38:35 -04:00
|
|
|
onEmbed={this.handleEmbed}
|
Feature conversations muting (#3017)
* Add <ostatus:conversation /> tag to Atom input/output
Only uses ref attribute (not href) because href would be
the alternate link that's always included also.
Creates new conversation for every non-reply status. Carries
over conversation for every reply. Keeps remote URIs verbatim,
generates local URIs on the fly like the rest of them.
* Conversation muting - prevents notifications that reference a conversation
(including replies, favourites, reblogs) from being created. API endpoints
/api/v1/statuses/:id/mute and /api/v1/statuses/:id/unmute
Currently no way to tell when a status/conversation is muted, so the web UI
only has a "disable notifications" button, doesn't work as a toggle
* Display "Dismiss notifications" on all statuses in notifications column, not just own
* Add "muted" as a boolean attribute on statuses JSON
For now always false on contained reblogs, since it's only relevant for
statuses returned from the notifications endpoint, which are not nested
Remove "Disable notifications" from detailed status view, since it's
only relevant in the notifications column
* Up max class length
* Remove pending test for conversation mute
* Add tests, clean up
* Rename to "mute conversation" and "unmute conversation"
* Raise validation error when trying to mute/unmute status without conversation
2017-05-14 21:04:13 -04:00
|
|
|
/>
|
2016-10-19 12:20:19 -04:00
|
|
|
|
2016-10-24 11:11:02 -04:00
|
|
|
{descendants}
|
2016-10-19 12:20:19 -04:00
|
|
|
</div>
|
|
|
|
</ScrollContainer>
|
2016-10-07 10:00:11 -04:00
|
|
|
</Column>
|
2016-09-15 18:21:51 -04:00
|
|
|
);
|
|
|
|
}
|
|
|
|
|
2017-04-21 14:05:35 -04:00
|
|
|
}
|