Select project page in react-admin
I'm working on a management dashboard using react-admin and I'm looking for a way to allow a user to login, select which project he wants to work on, and only then show him the dashboard with data specific to the selected project.
Something like the way the firebase console works.
What's the best way to create something like this?
EDIT
In response to linguamachina's very friendly advice I'll add some more details:
I'm not looking for UI or UX solutions. I'm using the react-admin library and I'm trying to understand what would be the best practice for this use case.
My data source looks something like this:
http://my_api_server/projects/project_id/some_resource/resource_id
Currently I've written my dataProvider so that it requires the project id on initialisation:
const dataProvider = myDataProvider(projectId)
const App = () => (
<Admin dataProvider={dataProvider}>
<Resource name="some_resource">
</Admin>
)
This works ok but I would like the option to change the project on the fly. If it's possible to send the project ID as an extra parameter in the resource request it could really solve this issue.
Alternatively, I though about saving the project ID into localStorage and getting it from there during requests.
I'm just looking for the most simple solution that can use as much of the built-in functionality of react-admin.
reactjs react-admin
add a comment |
I'm working on a management dashboard using react-admin and I'm looking for a way to allow a user to login, select which project he wants to work on, and only then show him the dashboard with data specific to the selected project.
Something like the way the firebase console works.
What's the best way to create something like this?
EDIT
In response to linguamachina's very friendly advice I'll add some more details:
I'm not looking for UI or UX solutions. I'm using the react-admin library and I'm trying to understand what would be the best practice for this use case.
My data source looks something like this:
http://my_api_server/projects/project_id/some_resource/resource_id
Currently I've written my dataProvider so that it requires the project id on initialisation:
const dataProvider = myDataProvider(projectId)
const App = () => (
<Admin dataProvider={dataProvider}>
<Resource name="some_resource">
</Admin>
)
This works ok but I would like the option to change the project on the fly. If it's possible to send the project ID as an extra parameter in the resource request it could really solve this issue.
Alternatively, I though about saving the project ID into localStorage and getting it from there during requests.
I'm just looking for the most simple solution that can use as much of the built-in functionality of react-admin.
reactjs react-admin
Your question is broad and opinion-based. Try to limit posts to a single question. As it stands you're asking about application design, technology choices, UX and UI all at once. You would do better if you research available options for each of your problem areas, and come back with specific questions once you have at least made an effort yourself.
– linguamachina
Nov 25 '18 at 12:04
add a comment |
I'm working on a management dashboard using react-admin and I'm looking for a way to allow a user to login, select which project he wants to work on, and only then show him the dashboard with data specific to the selected project.
Something like the way the firebase console works.
What's the best way to create something like this?
EDIT
In response to linguamachina's very friendly advice I'll add some more details:
I'm not looking for UI or UX solutions. I'm using the react-admin library and I'm trying to understand what would be the best practice for this use case.
My data source looks something like this:
http://my_api_server/projects/project_id/some_resource/resource_id
Currently I've written my dataProvider so that it requires the project id on initialisation:
const dataProvider = myDataProvider(projectId)
const App = () => (
<Admin dataProvider={dataProvider}>
<Resource name="some_resource">
</Admin>
)
This works ok but I would like the option to change the project on the fly. If it's possible to send the project ID as an extra parameter in the resource request it could really solve this issue.
Alternatively, I though about saving the project ID into localStorage and getting it from there during requests.
I'm just looking for the most simple solution that can use as much of the built-in functionality of react-admin.
reactjs react-admin
I'm working on a management dashboard using react-admin and I'm looking for a way to allow a user to login, select which project he wants to work on, and only then show him the dashboard with data specific to the selected project.
Something like the way the firebase console works.
What's the best way to create something like this?
EDIT
In response to linguamachina's very friendly advice I'll add some more details:
I'm not looking for UI or UX solutions. I'm using the react-admin library and I'm trying to understand what would be the best practice for this use case.
My data source looks something like this:
http://my_api_server/projects/project_id/some_resource/resource_id
Currently I've written my dataProvider so that it requires the project id on initialisation:
const dataProvider = myDataProvider(projectId)
const App = () => (
<Admin dataProvider={dataProvider}>
<Resource name="some_resource">
</Admin>
)
This works ok but I would like the option to change the project on the fly. If it's possible to send the project ID as an extra parameter in the resource request it could really solve this issue.
Alternatively, I though about saving the project ID into localStorage and getting it from there during requests.
I'm just looking for the most simple solution that can use as much of the built-in functionality of react-admin.
reactjs react-admin
reactjs react-admin
edited Nov 27 '18 at 8:13
Nadevo
asked Nov 25 '18 at 11:39
NadevoNadevo
11
11
Your question is broad and opinion-based. Try to limit posts to a single question. As it stands you're asking about application design, technology choices, UX and UI all at once. You would do better if you research available options for each of your problem areas, and come back with specific questions once you have at least made an effort yourself.
– linguamachina
Nov 25 '18 at 12:04
add a comment |
Your question is broad and opinion-based. Try to limit posts to a single question. As it stands you're asking about application design, technology choices, UX and UI all at once. You would do better if you research available options for each of your problem areas, and come back with specific questions once you have at least made an effort yourself.
– linguamachina
Nov 25 '18 at 12:04
Your question is broad and opinion-based. Try to limit posts to a single question. As it stands you're asking about application design, technology choices, UX and UI all at once. You would do better if you research available options for each of your problem areas, and come back with specific questions once you have at least made an effort yourself.
– linguamachina
Nov 25 '18 at 12:04
Your question is broad and opinion-based. Try to limit posts to a single question. As it stands you're asking about application design, technology choices, UX and UI all at once. You would do better if you research available options for each of your problem areas, and come back with specific questions once you have at least made an effort yourself.
– linguamachina
Nov 25 '18 at 12:04
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53467064%2fselect-project-page-in-react-admin%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53467064%2fselect-project-page-in-react-admin%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Your question is broad and opinion-based. Try to limit posts to a single question. As it stands you're asking about application design, technology choices, UX and UI all at once. You would do better if you research available options for each of your problem areas, and come back with specific questions once you have at least made an effort yourself.
– linguamachina
Nov 25 '18 at 12:04