我创建了一个Relay.Mutation
,它应该触发User
个对象的更新:
class UserMutation extends Relay.Mutation {
public getMutation() {
return Relay.QL`mutation {saveUser}`;
}
public getVariables() {
return {
id: this.props.user.id,
loginName: this.props.user.loginName,
firstName: this.props.user.firstName,
lastName: this.props.user.lastName,
mail: this.props.user.mail
}
}
public getFatQuery() {
return Relay.QL`
fragment on UserPayload {
user {
id,
loginName,
firstName,
lastName,
mail
}
}
`;
}
public getConfigs() {
return [{
type: "FIELDS_CHANGE",
fieldIDs: {
user: this.props.user.id
}
}];
}
static fragments = {
user: () => Relay.QL`
fragment on User {
id,
// I initially had only id here
loginName,
firstName,
lastName,
mail
}
`
}
}
我在我的组件UserDetails
中使用此突变,如下所示:
// I initially passed this.props.user to the mutation
this.props.relay.commitUpdate(new UserMutation({ user: this.state.user })
执行时,中继将user
传递给后端,只设置id
,没有任何其他属性。突变未执行,因为输入变量缺少其他字段。
在调试变异后,我看到this.props.user
已在所有字段上设置undefined
但是id。但是,this._unresolvedProps.user
是user
,所有字段设置正确。
当我更改变异代码并将所有this.props
替换为this._unresolvedProps
时,所有必要的数据都会传输到后端,并且执行变异时没有任何错误。前端缓存似乎也正确更新(像firstName
这样的字段在其他组件中更新)。但我不认为这是正确的方法。
我想念什么?
更新
UserDetails
组件加载用户数据,如loginName
,并提供更改这些属性的文本框。相应的中继容器如下所示:
export default Relay.createContainer(UserDetails, {
fragments: {
user: () => Relay.QL`
fragment on User {
id,
loginName,
firstName,
lastName,
mail,
roles {
id,
name
},
${UserMutation.getFragment("user")}
}
`
}
});
我处理文本输入处理程序中的文本框更改...
public handleTextInput(fieldName: string, event: any) {
let user = this.state.user;
switch (fieldName) {
case "loginName": {
user.loginName = event.target.value;
break;
}
case "firstName": {
user.firstName = event.target.value;
break;
}
case "lastName": {
user.lastName = event.target.value;
break;
}
case "mail": {
user.mail = event.target.value;
break;
}
}
this.setState({ user: user });
}
...并在提交处理程序中提交表单,我现在将this.state.user
传递给突变:
public handleSubmit(e: any) {
e.preventDefault();
this.props.relay.commitUpdate(new UserMutation({ user: this.state.user }), {
onSuccess: (response: any) => {
this.setState({ user: response.saveUser.user });
}
});
}
我使用C#后端:graphql-dotnet。这就是我为突变定义的内容:
public class ApplicationSchema : Schema
{
public ApplicationSchema()
{
this.Query = new ApplicationQuery();
this.Mutation = new ApplicationMutation();
}
}
public class ApplicationMutation : ObjectGraphType
{
public ApplicationMutation()
{
this.Name = "Mutation";
// save a user
this.Field<UserPayloadType>(
"saveUser",
arguments: new QueryArguments(
new QueryArgument<NonNullGraphType<UserInputType>>
{
Name = "input",
Description = "the user that should be saved"
}),
resolve: context =>
{
var userInput = context.Argument<UserInput>("input");
var clientMutationId = userInput.ClientMutationId;
var user = MemoryRepository.UpdateUser(new User()
{
Id = userInput.Id,
LoginName = userInput.LoginName,
FirstName = userInput.FirstName,
LastName = userInput.LastName,
Mail = userInput.Mail
});
return new UserPayload()
{
ClientMutationId = clientMutationId,
User = user
};
});
}
}
public class UserInputType : InputObjectGraphType
{
public UserInputType()
{
this.Name = "UserInput";
this.Field<NonNullGraphType<StringGraphType>>("id", "The id of the user.");
this.Field<NonNullGraphType<StringGraphType>>("loginName", "The login name of the user.");
this.Field<NonNullGraphType<StringGraphType>>("firstName", "The first name of the user.");
this.Field<NonNullGraphType<StringGraphType>>("lastName", "The last name of the user.");
this.Field<NonNullGraphType<StringGraphType>>("mail", "The mail adress of the user.");
this.Field<NonNullGraphType<StringGraphType>>("clientMutationId", "react-relay property.");
}
}
public class UserPayloadType : ObjectGraphType
{
public UserPayloadType()
{
this.Name = "UserPayload";
this.Field<NonNullGraphType<UserType>>("user", "The user.");
this.Field<NonNullGraphType<StringGraphType>>("clientMutationId", "react-relay property.");
}
}
public class UserType : ObjectGraphType
{
public UserType()
{
this.Name = "User";
this.Field<NonNullGraphType<StringGraphType>>("id", "The id of the user.");
this.Field<NonNullGraphType<StringGraphType>>("loginName", "The login name of the user.");
this.Field<NonNullGraphType<StringGraphType>>("firstName", "The first name of the user.");
this.Field<NonNullGraphType<StringGraphType>>("lastName", "The last name of the user.");
this.Field<NonNullGraphType<StringGraphType>>("mail", "The mail adress of the user.");
Field<ListGraphType<RoleType>>("roles", resolve: context => MemoryRepository.GetRolesOfUser(context.Source as DomainModel.Models.User));
}
}
答案 0 :(得分:2)
您的Relay容器是否正确提取User
片段?我在你的static fragments
定义片段中看到User is only id字段,所以我想知道你的父Relay组件是否全部取出它们。
由于您的变异确实依赖于这些字段,因此请将它们添加到fragments
属性。
class UserMutation extends Relay.Mutation {
public getMutation() { ... }
// getVariables, FatQuery and Configs ...
static fragments = {
user: () => Relay.QL`
fragment on User {
id,
loginName,
firstName,
lastName,
mail
}
`
}
}
然后尝试将此片段包含在使用您的突变的Relay组件中。 示例React-Relay组件:
import UserMutation from 'mutations/user';
class User extends Component {
commit(e) {
Relay.Store.commitUpdate(
new UserMutation({
user: this.props.user
})
);
}
render() {
return (
<div>Hello</div>
);
}
};
export default Relay.createContainer(User, {
fragments: {
user: () => Relay.QL`
fragment on User {
${UserMutation.getFragment('user')}
}
`,
}
});
答案 1 :(得分:0)
使用 REQUIRED_CHILDREN 并更新组件中的状态。
您可以使用REQUIRED_CHILDREN而不是使用FIELDS_CHANGE,这样您就可以将返回的已保存对象添加到商店中。你要做的是设置你的getConfigs:
getConfigs() {
return [{
type: 'REQUIRED_CHILDREN',
children: [
Relay.QL`
fragment on UserPayload {
user {
id
loginName
firstName
lastName
mail
}
}
`
]
}]
}
在改变你的commitUpdate时:
this.props.relay.commitUpdate(
new UserMutation({user: this.props.user}),
{
onSuccess: response => this.setState({
user: response.user,
}),
onError: err => console.log(err)
}
);
如您所见,onSuccess回调使您可以调用actionCreator并将新用户置于应用程序的状态。您可以使用您在应用程序中使用的任何状态管理。在这种情况下,它只是setState。
REQUIRED_CHILDREN配置用于将其他子项附加到变异查询中。例如,您可能需要使用它来获取由变异创建的新对象上的字段(以及Relay通常不会尝试获取的字段,因为它之前没有为该对象提取任何内容)。
由于REQUIRED_CHILDREN配置而获取的数据未写入客户端存储,但您可以在传递给commitUpdate()
的onSuccess回调中添加处理它的代码。
There is more information in the documentation about REQUIRED_CHILDREN here.