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

Grey-out buttons after submission #443

Open
jamesrwelch opened this issue Jan 26, 2022 · 4 comments · May be fixed by #457
Open

Grey-out buttons after submission #443

jamesrwelch opened this issue Jan 26, 2022 · 4 comments · May be fixed by #457
Assignees
Labels
bug Something isn't working enhancement New feature or request good first issue Good for newcomers

Comments

@jamesrwelch
Copy link
Contributor

The UI should probably disable buttons after they've been clicked, until a response is received. This would stop multiple requests being made in error. For example, the 'submit data model' button on creating a new data model, allows several clicks and may make several requests.
Screenshot 2022-01-26 at 11 43 08

There are almost certainly other examples in other places.

@jamesrwelch jamesrwelch added bug Something isn't working enhancement New feature or request good first issue Good for newcomers labels Jan 26, 2022
@shikhavani
Copy link

Hi @jamesrwelch , I am willing to solve this issue, but after serving the app, I am not getting the response from APIs.
image

@pjmonks
Copy link
Contributor

pjmonks commented Jan 31, 2022

Hi @shikhavani . Are you able to check if you have a running instance of the Mauro backend? During development of the UI, the default API endpoint is configured to be http://localhost:8080/api, so do you have a running Mauro web service on that address/port?

If not we can run you through the steps to get ready.

@shikhavani
Copy link

shikhavani commented Jan 31, 2022 via email

@pjmonks
Copy link
Contributor

pjmonks commented Jan 31, 2022

Apologies for that @shikhavani , there should be something to explain how to setup the UI end-to-end. I'll add a new issue to update the README.

In the meantime, you'll need to follow some of the steps in these two other repo README's:

  1. mdm-core - explains what dependencies you will need - Grails, Postgres etc
  2. mdm-application-build - this is the repo you'll need to get a running backend instance. This is a Grails app which uses the latest mdm-core code to run.

If you need any other help, please take a look at the https://maurodatamapper.github.io/community/contribute/ page, this can also point you to the Zulip community chat so you can ask further questions to other people.

cc @jamesrwelch

shikhavani pushed a commit to shikhavani/mdm-ui that referenced this issue Feb 2, 2022
shikhavani pushed a commit to shikhavani/mdm-ui that referenced this issue Feb 2, 2022
shikhavani pushed a commit to shikhavani/mdm-ui that referenced this issue Feb 2, 2022
shikhavani pushed a commit to shikhavani/mdm-ui that referenced this issue Feb 2, 2022
shikhavani pushed a commit to shikhavani/mdm-ui that referenced this issue Feb 2, 2022
shikhavani pushed a commit to shikhavani/mdm-ui that referenced this issue Feb 2, 2022
@pjmonks pjmonks linked a pull request Feb 5, 2022 that will close this issue
@jamesrwelch jamesrwelch moved this to Backlog in MDM State Mar 7, 2022
@NigelPalmer NigelPalmer moved this from Backlog to Fix for next release in MDM State Jan 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request good first issue Good for newcomers
Projects
Status: Fix for next release
Development

Successfully merging a pull request may close this issue.

3 participants