Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Value don't saved if field used exceptOnForms() or hideWhenUpdating() #24

Open
4n70w4 opened this issue Feb 6, 2020 · 3 comments
Open
Labels
question Further information is requested

Comments

@4n70w4
Copy link
Contributor

4n70w4 commented Feb 6, 2020

            InlineSelect::make(__('Status'), 'status')
                ->options([...])
                ->exceptOnForms()
                ->inlineOnIndex()->inlineOnDetail(),
@4n70w4 4n70w4 changed the title Value don't saved if field used exceptOnForms() Value don't saved if field used exceptOnForms() or hideWhenUpdating() Feb 6, 2020
@4n70w4
Copy link
Contributor Author

4n70w4 commented Feb 6, 2020

Workaround:

                ->canSee(function (NovaRequest $request) {
                    return false === $request->isUpdateOrUpdateAttachedRequest() && false === $request->isCreateOrAttachRequest();
                })

@brandonferens
Copy link
Member

Thanks @4n70w4. I am curious, however, the use case for adding exceptOnForms(). The behavior of this field is just display on the index and/or detail views.

@brandonferens brandonferens added the question Further information is requested label Feb 6, 2020
@4n70w4
Copy link
Contributor Author

4n70w4 commented Feb 7, 2020

Editing a record and changing status are two different events. Allows to make do both at the same time from a single screen - is unacceptable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants