abstratt / kirra Goto Github PK

bogus

Expose the supertypes of an entity.

Required to support abstratt/kirra-ui#12.

Provide support for determining the sub entities of a base entity.

...so that a UI can show them to the user before the user submits the action.

Currently, clients need to fall back to using the entity extent.

If a user is logged in, include a link to the user instance in the application index resource.

REST API should not show non-user visible properties.

We are missing URLs for queries/actions in entity definition, so a client has no clue on how to issue them.

Expose instances of subtypes in an entity's extent. Use a query parameter to decide whether to do so (by default don't)

Case in question: https://github.com/abstratt/cloudfier-sustainable-jersey/tree/master/vacant-properties

Or maybe not. But the "Load Database" feature is not working with blobs at this time (loads metadata but not the data).

Unlinking needs to be subtype-aware. Numeric ids are not globally unique, need the related type info as well.

Support access via HTTPS. If a request is made through https, links returned ought to be for the same protocol. It currently returns http URIs.

data.json validation fails if null is provided for a relationship:

Deploy failed: ERROR: null expected to be an object or reference - data.json : 1

    private void validateReferenceOrInstance(String currentNamespace, JsonNode jsonNode, TypeRef typeRef) {
        if (jsonNode.isTextual()) {
            validateReference(typeRef, currentNamespace, jsonNode);
        } else if (jsonNode.isObject()) {
            Entity referredEntity = schema.getEntity(typeRef.getEntityNamespace(), typeRef.getTypeName());
            validateInstance(referredEntity, jsonNode);
        } else {
            collector.addError(jsonNode + " expected to be an object or reference");
            return;
        }
    }

Instance creation is returning status 200 instead of 201.

bogus

REST API should not include links when returning list of instances. A client can see those with the instance simple resource.

For instance, in capabilities, that are all mixed up right now. Why is this important? Clients need to do filtering all the time. In contexts where real queries are used, metrics are not, and vice-versa.

Provide support for attachments/blobs. Most applications need that.

Add support for images.

See summary.

bogus

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• Update dependency org.codehaus.mojo:build-helper-maven-plugin to v3.5.0

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency grunt to v1.5.3 [SECURITY]
• Update actions/checkout action to v4
• Update actions/setup-java action to v4
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Expose parameter sets in kirra.

See abstratt/textuml#134.

It should be easy to switch to another entity's instance list from anywhere in the application. Right now you need to hit Back multiple times until you get to the Main screen. The Main screen might even become unnecessary.

Allow creating a profile.

In addition to the basic user information the server needs, we will need also information for each of the roles the user has.

Support finders in the REST API.

Also, it allows the user to attempt to change it, but it does not make the required change.

java.lang.IllegalStateException: Expected BEGIN_OBJECT but was BEGIN_ARRAY
at com.google.gson.internal.bind.JsonTreeReader.expect(JsonTreeReader.java:139)
at com.google.gson.internal.bind.JsonTreeReader.beginObject(JsonTreeReader.java:70)
at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:165)
... 96 more

When editing an existing record, could show the instance shorthand (and remove it from the form if not editable).

When adding a new one, could just show 'New Foo'.

Right now, clients need to list all results and count (!!!) them.

If an entity has no editable fields, do not show Save button when opening an existing record.

Reflect the fact that instance links are single-valued. We have decided a while ago to use a special getRelatedInstances API to retrieve multivalued links instead of expecting them to be inlined.

Add support for ng-admin.