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

numerical tags causes serious problem! #11193

Closed
nazarifard opened this issue Jul 15, 2024 · 9 comments · Fixed by #11194
Closed

numerical tags causes serious problem! #11193

nazarifard opened this issue Jul 15, 2024 · 9 comments · Fixed by #11194
Labels
Priority:p2-high Escalation, on top of current planning, release blocker Type:Bug Something isn't working

Comments

@nazarifard
Copy link
Contributor

if user add number as a tag to one folder, the folder will be missed entirely!
for example; adding 1234 as a tag will cause the resource disappear totally.

@nazarifard nazarifard added the Type:Bug Something isn't working label Jul 15, 2024
@phil-davis
Copy link
Contributor

@PrajwolAmatya do we have some test coverage for tags, and the case where a tag is numeric?

@nazarifard
Copy link
Contributor Author

@PrajwolAmatya do we have some test coverage for tags, and the case where a tag is numeric?

Yes, just assign a 1234 as a tag to a folder and press enter. I can't show the result because OCIS doesn't work after this case and can't show the parent folder that contains any resource with numeric tags!

@nazarifard
Copy link
Contributor Author

image

after refresh the page, OCIS can't find the resource.

image

@PrajwolAmatya
Copy link
Contributor

@PrajwolAmatya do we have some test coverage for tags, and the case where a tag is numeric?

I can reproduce this, adding numeric tag and refreshing the page the oCIS stops working.
We do have test cases for tags but not specifically with the numerical tags. I will create a separate issue to add tests for adding numeric tags to a resource.

@kobergj
Copy link
Contributor

kobergj commented Jul 16, 2024

Awesome. You loose your complete personal space if you add numerical tags to a resource. Works also in project spaces. Needs a fix asap.

@kobergj kobergj self-assigned this Jul 16, 2024
@kobergj kobergj transferred this issue from owncloud/ocis Jul 16, 2024
@kobergj kobergj removed their assignment Jul 16, 2024
@kobergj
Copy link
Contributor

kobergj commented Jul 16, 2024

Web throws error:

TypeError: (e.props[D.Tags] || "").split is not a function

nazarifard added a commit to nazarifard/web that referenced this issue Jul 16, 2024
@nazarifard
Copy link
Contributor Author

Awesome. You loose your complete personal space if you add numerical tags to a resource. Works also in project spaces. Needs a fix asap.

I fixed the issue independently, However first part is also fixed by @AlexAndBear
But I think it's a It is the tip of the iceberg, likely at least all property of DavPropertyMapping should be double checked.

nazarifard added a commit to nazarifard/web that referenced this issue Jul 16, 2024
@nazarifard
Copy link
Contributor Author

Hi @AlexAndBear
I sent a new PR to fix the issue, but seemingly there is a issue in TestFunctions and my PR is blocked. Can you review the source and or Unit Test functions. I tested locally and my codes is working fine without any issue.

#11197

@AlexAndBear
Copy link
Contributor

AlexAndBear commented Jul 16, 2024

@nazarifard
Looks like the CI is green, I don't see any failing tasks.
Thank you very much, merged.

AlexAndBear added a commit that referenced this issue Jul 16, 2024
@AlexAndBear AlexAndBear added the Priority:p2-high Escalation, on top of current planning, release blocker label Jul 16, 2024
JammingBen pushed a commit that referenced this issue Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:p2-high Escalation, on top of current planning, release blocker Type:Bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

5 participants