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

Added Concept scheme and two test concepts. The UI was not updated to show the actual concept names #1356

Open
mparsons-ce opened this issue May 2, 2024 · 17 comments
Assignees
Labels
blocker Holding up work in other projects. bug Unintended behavior. Concept Scheme Credential Engine CaSS

Comments

@mparsons-ce
Copy link

@Lomilar
Added concept scheme: ce-3f0a4095-c455-4209-acfe-ac0486f74e78
On click of Done, the UI still shows the default name of New Concept Scheme.
I created two concepts Concept 1, and Concept 2, but the UI shows the default names of New Concept.

@mparsons-ce mparsons-ce added bug Unintended behavior. blocker Holding up work in other projects. Concept Scheme labels May 2, 2024
@mparsons-ce
Copy link
Author

Also on attempts to edit the concept scheme, I would get a similar error to the progression model issue: that publication status must be selected, where it already is.
image

@Lomilar
Copy link
Member

Lomilar commented May 15, 2024

This still can occur, but clicking on and then off the box can clear the issue now. Leaving this open.

@winonadeb
Copy link

since there is a workaround, perhaps this is not a blocker just a bug?

@sedula27
Copy link

The save/update names works on production, but sandbox remains the same.

Issue with the required fields(Description/Publication Status) highlighted even though they are filled still persists

@sedula27
Copy link

Issue with the required fields(Description/Publication Status) highlighted even though they are filled, this is not a consistent issue

@miledivovic
Copy link
Contributor

@sedula27 I'm trying to replicate this issue on https://sandbox.credentialengine.org/ currently and am unable to do so. This may already be fixed, can you confirm if this is the case?

@sedula27
Copy link

sedula27 commented Jul 9, 2024

@miledivovic The issue with adding a concept scheme/Progression model right now is, it does not recognize the Publication status type even though there is a value there, refer to #1346. The current work around for adding a concept scheme without the publication status type is
This still can occur, but clicking on and then off the box can clear the issue now. Leaving this open. as Fritz mentioned above

@miledivovic
Copy link
Contributor

@sedula27 I'm not able to reproduce the issue with the publication status type either, the concept scheme is able to save without needing to click on and off the box

@sedula27
Copy link

sedula27 commented Jul 9, 2024

@miledivovic I did try just now and I was not able to add a concept scheme without publication status type throwing an error, refer screen recording attached

Credential.Publisher._.Concept.Schemes.-.Google.Chrome.2024-07-09.16-27-11.mp4

@miledivovic
Copy link
Contributor

miledivovic commented Jul 9, 2024

@sedula27 Interesting, I wonder if maybe there is some caching going on resulting in you not being given the most recent version of the cass editor... because this exact scenario is working fine for me. Could you try to reproduce this in an incognito window to rule out caching as the issue?

@sedula27
Copy link

sedula27 commented Jul 9, 2024

Thanks @miledivovic This works for a concept scheme when I tried it in my incognito window and my browser after clearing cache. Can you try the same for a progression model, i get the same error

Credential.Publisher._.Progression.Models.-.Google.Chrome.2024-07-09.16-59-17.mp4

@miledivovic
Copy link
Contributor

@sedula27 Hmm thats strange, for me the progression models are also working normally

@sedula27
Copy link

sedula27 commented Jul 10, 2024

@miledivovic When I try the same now for a concept scheme I do see the publication status error in an incognito window

@sedula27
Copy link

Error in the console
main.js:39 Uncaught (in promise) TypeError: Failed to execute 'fetch' on 'Window': Failed to read the 'headers' property from 'RequestInit': The provided value is not of type '(record<ByteString, ByteString> or sequence<sequence>)'.
at _callee$ (main.js:39:36)
at tryCatch (regeneratorRuntime.js:45:16)
at Generator. (regeneratorRuntime.js:133:17)
at Generator.next (regeneratorRuntime.js:74:21)
at asyncGeneratorStep (asyncToGenerator.js:3:24)
at _next (asyncToGenerator.js:22:9)
at asyncToGenerator.js:27:7
at new Promise ()
at asyncToGenerator.js:19:12
at editor.js:284:13

@sedula27
Copy link

@miledivovic
Copy link
Contributor

@sedula27 This should be fixed now on sandbox

@sedula27
Copy link

sedula27 commented Aug 7, 2024

This is fixed on sandbox and has been verified

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker Holding up work in other projects. bug Unintended behavior. Concept Scheme Credential Engine CaSS
Projects
None yet
Development

No branches or pull requests

6 participants