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

Add standarized competencies not working #10396

Open
NadeoWolf opened this issue Feb 24, 2025 · 7 comments
Open

Add standarized competencies not working #10396

NadeoWolf opened this issue Feb 24, 2025 · 7 comments
Labels
atlas Pull requests that affect the corresponding module bug

Comments

@NadeoWolf
Copy link

Describe the bug

Adding standarized competenzies is not working.

To Reproduce

  1. Go to Server Administration
  2. Click on Standarized Competencies
  3. Click on the + Button (Create knowledge Area)

Expected behavior

Some sort of reaction. new Page, popup or something else.

Screenshots

Image

Which version of Artemis are you seeing the problem on?

7.10.3

What browsers are you seeing the problem on?

Other (specify in "Additional context")

Additional context

Brave and Chrome

Relevant log output

No Log in Artemis or NGINX

Browser Log Message:

standardized-competencies:1 Blocked aria-hidden on an element because its descendant retained focus. The focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor. Consider using the inert attribute instead, which will also prevent focus. For more details, see the aria-hidden section of the WAI-ARIA specification at https://w3c.github.io/aria/#aria-hidden.
Element with focus: button
Ancestor with aria-hidden:  <jhi-app ng-version=​"19.1.7" _nghost-ng-c3821447986><jhi-alert-overlay _ngcontent-ng-c3821447986 _nghost-ng-c1900799148 class=​"ng-tns-c1900799148-0">​flex<!----><!----></jhi-alert-overlay><div _ngcontent-ng-c3821447986 id=​"page-wrapper" cdkscrollable class=​"page-wrapper" style=​"overflow-y:​ auto;​"><jhi-page-ribbon _ngcontent-ng-c3821447986 _nghost-ng-c3913610564>​…​</jhi-page-ribbon><div _ngcontent-ng-c3821447986 class=​"sticky-top-navbar ng-star-inserted">​…​</div><!----><div _ngcontent-ng-c3821447986 class=​"card ng-star-inserted" style=​"border-style:​ none;​">​…​</div>​flex<!----><!----><jhi-notification-popup _ngcontent-ng-c3821447986 _nghost-ng-c2953551212>​…​</jhi-notification-popup><div _ngcontent-ng-c3821447986 class=​"ng-star-inserted">​…​</div><!----></div></jhi-app>
@NadeoWolf NadeoWolf added the bug label Feb 24, 2025
@github-actions github-actions bot added atlas Pull requests that affect the corresponding module communication Pull requests that affect the corresponding module lecture Pull requests that affect the corresponding module text Pull requests that affect the corresponding module labels Feb 24, 2025
@krusche krusche removed communication Pull requests that affect the corresponding module lecture Pull requests that affect the corresponding module text Pull requests that affect the corresponding module labels Feb 24, 2025
@krusche krusche added this to Atlas Feb 24, 2025
@MaximilianAnzinger MaximilianAnzinger moved this to Backlog in Atlas Mar 6, 2025
@MaximilianAnzinger
Copy link
Collaborator

Thank you for pointing this out. It seems like this is also related to the new modularization of Artemis. We're looking into it.

@ole-ve
Copy link
Contributor

ole-ve commented Mar 7, 2025

To me, this seems unrelated to the modularisation. But rather to the fact that the dialog for creating knowledge areas does not render (on the right-hand side) if no knowledge area exist yet (chicken-egg).

Code Pointers:

  • webapp/app/admin/standardized-competencies/standardized-competency-management.component.html: @if (dataSource.data?.length)

Image

@ole-ve
Copy link
Contributor

ole-ve commented Mar 7, 2025

@NadeoWolf as a workaround until fixed, you could import knowledge areas with the button on the top right (dummy content, example is given). Then, you should be able to add new ones (and remove the old one)

@NadeoWolf
Copy link
Author

@ole-ve i tried that before. But if i use the example it tells me "Unable to parse file. Please upload a file with valid JSON syntax"

I removed the comments because that is not valid JSON.

Image

example.json

@ole-ve
Copy link
Contributor

ole-ve commented Mar 7, 2025

The example file is not valid JSON (as taken from the page). You would need to remove the commas after the "sourceId" and "children" elements like here: example.json.

We should adapt this in the same PR @MaximilianAnzinger

@NadeoWolf
Copy link
Author

  1. children cannot be empty. but now its working for me. example3.json Thx @ole-ve

  2. I found no CRUD-UI for Sources

@ole-ve
Copy link
Contributor

ole-ve commented Mar 7, 2025

I found no CRUD-UI for Sources

Couldn't see it during the import, but it seems to be listed after the import, right? Sorry, I am not really into the atlas functionality 🙃

After importing the example3.json:
Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
atlas Pull requests that affect the corresponding module bug
Projects
Status: Backlog
Development

No branches or pull requests

4 participants