Project

General

Profile

Actions
Copy link

Bug #2358

closed

ID search doesn't work

Added by Bernhard Koschiček-Krombholz 2 months ago. Updated 2 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Olivia Reichl
Target version:
0.7.0
Start date:
2024-10-09
Estimated time:
Found in version:
0.6.0

Description

The problem is, that the IDs are parsed as string and not number (int), e.g. link

Related issues 1 (0 open — 1 closed)

Related to OpenAtlas - Feature #2365: API 0.4.5ClosedBernhard Koschiček-Krombholz2024-10-11Actions
Actions
Copy link
 #1

Updated by Alexander Watzinger 2 months ago

  • Status changed from New to Assigned
  • Assignee set to Olivia Reichl
  • Target version set to 0.7.0
  • Found in version set to 0.6.0
Actions
Copy link
 #2

Updated by Olivia Reichl 2 months ago

  • Assignee changed from Olivia Reichl to Bernhard Koschiček-Krombholz
Actions
Copy link
 #3

Updated by Bernhard Koschiček-Krombholz 2 months ago

Actions
Copy link
 #4

Updated by Bernhard Koschiček-Krombholz 2 months ago

  • Assignee changed from Bernhard Koschiček-Krombholz to Olivia Reichl

I changed the search parameter in this way, that you can now use string numbers. If any other character is included, an error is thrown.

But I noticed that the request also uses the operator like. This is not available for any ID searches. For ID searches like entityID, typeID, valueTypeID or typeIDWithSubs you can only use equal or notEqual. In the new OpenAPI/Swagger definition (0.4.5a) I made a table, which operator is available for which category.

Since the dev-demo is on another version than the original develop, I will ask Alex to update the demo-dev.

Actions
Copy link
 #5

Updated by Olivia Reichl 2 months ago

  • Status changed from Assigned to Closed
Actions
Copy link

Also available in: Atom PDF