speckleworks / speckleadmin Goto Github PK

Step 0:

• [x ] I've read the contribution guidelines!

Expected Behaviour

Access child stream smoothly

Actual Behaviour

What's actually going on!

Affected Projects

@didimitrie to be checked, i dont know

Proposed Solution (if any)

replace & with ? in the URL

Step 0:

• I've read the contribution guidelines!

The viewer's progress bar is currently indeterminate, even if it is actually a determinate process (number of object request buckets left).

Flagging this up as it's rather stupid not to properly display model loading progress when we actually can (consider adding a percentage info somewhere too, as the bar itself is rather abstract).

This would allow for it to be reused in other apps decently rather than by copy paste/iframe methods.

Step 0:

• I've read the contribution guidelines!

Proposed Solution (if any)

1. Do not display child streams in main admin viewer
2. Allow child deletion only from parent stream

The viewer progress bar keeps showing when an empty stream is loaded.

Also, it could be helpful displaying some text like "This stream is empty"

Step 0:

• I've read the contribution guidelines!

Expected Behaviour

In this stream the spheres are the endpoints of the arcs.

Actual Behaviour

Obvs, they're not 😢

In the speckle streams viewer, it would be nice to have a button/dropdown to 'add stream to project'

and allow peeps to edit their details

Step 0:

• I've read the contribution guidelines!

To make things compatible with this: speckleworks/SpeckleServer#77

Step 0:

• I've read the contribution guidelines!

Expected Behaviour

Extrusions seem to be not really working with non-solid ones. A single/curve/polyline/polycurve line is extruded in an open surface, but threejs fills it up.

Affected Projects

Does this issue propagate to other dependencies or dependants? If so, list them here!

Reproduction Steps & System Config (win, osx, web, etc.)

StreamId: B1zNJbklm @ speckle hestia

Step 0:

• I've read the contribution guidelines!

The trash route is janky, as if you have too many streams it creates 100s of DOM elements.

Proposed solution: paginate it, and potentially do not display stream clones.

Step 0:

• I've read the contribution guidelines!

Expected Behaviour

Write permissions for project owners displayed as default

Actual Behaviour

Whilst I am the project owner Speckle Admin shows I have read permissions only for both streams/project. Display bug?

Affected Projects

WS

Reproduction Steps & System Config (win, osx, web, etc.)

Proposed Solution (if any)

To talk with @PaulPoinet
Basically we need to somehow handle objects and their sub-objects.

Tasks:

• do not display in main list
• have option to search through them or display them at one point

Step 0:

• I've read the contribution guidelines!

Expected Behaviour

It would be great if the sharing link would also include the property filtering and object selection. This would let you share links about a specific object or properties, or otherwise provide different "views" into a stream with different links.

I.e. https://hestia.speckle.works/#/view/<streamId>?properties.coolness_factor

Actual Behaviour

The sharing link just shares the stream ID, i.e. https://hestia.speckle.works/#/view/<streamId>

Proposed Solution (if any)

Include the query filter in the shareable link.

I'm getting the error "This stream is not marked as online editable." on the data tab in my stream. How cam I change this?

Step 0:

• I've read the contribution guidelines!

Buttons to add:

• Camera FOV (possibly related #41)
• Zoom Extents
• Zoom To Object

Step 0:

• I've read the contribution guidelines!

Title says it all. StreamId to reproduce: R_VnfU7PG7 (@Hestia); actual polyline object is here. Note that the first and last vertex are duplicated (as should be), and that the export is correct (closed: true).

It's probably a bug introduced when I switched to buffer geometry for polylines...

Step 0:

• I've read the contribution guidelines!

Expected Behaviour

Creating a data object via the web interface should create a named object using the input name, with its value field set to the input data.

Actual Behaviour

Creating a data object via the web interface creates a new layer with the input name, and an object without a name (it is null) and its value field set to the input data.

Affected Projects

Does this issue propagate to other dependencies or dependants? If so, list them here!

Not sure.

Reproduction Steps & System Config (win, osx, web, etc.)

Proposed Solution (if any)

Create named objects from the web interface: name becomes the object's name field, data becomes the object's value field.

Step 0:

• I've read the contribution guidelines!

Expected Behaviour

In the right side panel there are 4 tabs across the top of the panel which allow you to toggle between 'search for streams', 'select property...', view code, and settings. These should always be accessible

Actual Behaviour

When the page is zoomed to a certain extent, the right hand panel auto-hides and after this point, the tabs across the top of the panel are no longer visible.

Affected Projects

nah

Reproduction Steps & System Config (win, osx, web, etc.)

• Open https://hestia.speckle.works/#/view in chrome
• zoom until the tool panel hides
• open the panel again to see if the tabs are still visible

e.g. https://www.dropbox.com/s/py3xp9lxc9je6hv/twinner%20-%20Google%20Chrome%2021.10.2019%2013_42_36.mp4?dl=0

Actual behaviour

I've successfully created a Speckle account with the API :

{
  "email": "[email protected]",
  "password": "testing",
  "name": "Radu",
  "surname": "Gidei",
  "company": "Grimshaw",
}

but if i try to log in to Speckle server using the Admin app, it validates the password field, requiring it to be longer than 8 characters.

Expected behaviour

I should be able to log in using my pre-existing password.
Whilst validation is expected on registration page, it shouldn't be on login page.

Step 0:

• I've read the contribution guidelines!

Expected Behaviour

Should point to: https://hestia.speckle.works/view/?streams=r1Q2Rzk1m

Actual Behaviour

Currently it links to: https://hestia.speckle.works/view/?r1Q2Rzk1m/v1

Allow to add remove users from several groups:

• read
• write
• comment

Extra: transfer ownership of stream

Step 0:

• I've read the contribution guidelines!

Allow to change the gradient colour range when colouring by a numeric property.

Step 0:

• I've read the contribution guidelines!

Expected Behaviour

The viewer should display all the curves present in the stream.

Actual Behaviour

The viewer shows less curves than it should :(

Reproduction Steps & System Config (win, osx, web, etc.)

Check this same stream on the API side and on the viewer side:
https://hestia.speckle.works/api/streams/GMmiyTy4z/
https://hestia.speckle.works/#/view/GMmiyTy4z
@didimitrie I gave you access

Proposed Solution (if any)

¯_(ツ)_/¯

This should reduce confusion about the purpose of the web app.

Hello there,
How do I change de Speckle Admin UI Port? Port 80 is in use by Apache already.

Last issue before release

Step 0:

• I've read the contribution guidelines!

Proposed Solution (if any)

Somewhere, potentially next to the stream data tab, have an interface that allows you to view the stream's data in a tabular form.

This should be coupled with a query building mechanism that directly pings the API, so that it can be used to create query links that people can then reuse to import data in excel.

It's an open ended question; for more reference see #32.

Step 0:

• I've read the contribution guidelines!

Zoom extents somehow still centres the scene with including the origin, as far as I understand.

To reproduce, load a model with geometry far off from the origin and press spacebar to zoom extents.

Step 0:

• I've read the contribution guidelines!

Expected Behaviour

If the accessed resource is public, display it. If the resource is private, show a notification.

Actual Behaviour

Because we don't set any server endpoint in the store, the requests do not end up anywhere, resulting in an invisible fail.

Reproduction Steps & System Config (win, osx, web, etc.)

Check this link out in a incognito/different browser (where you have never authenticated on the test server before).

Proposed Solution (if any)

Two ways:

1. Either assume the server is always at ${rootUrl}/api
2. Or add sharing buttons everywhere that append a ?server=${server api endpoint} to the link, and always check for that query param in the router or somewhere early on in the app init lifecycle, before any requests to the api are actually sent.

(1) works if we always have the plugins served by the server. (2) works if, for instance, we want to have a centrally deployed front end application that can service multiple servers.

(2) is a potentially future valid scenario, in the case of some deployments; (1) is nicer and cleaner to implement.

¯_(ツ)_/¯

Step 0:

• I've read the contribution guidelines!

Expected Behaviour

It should find it

Actual Behaviour

It does not find it

Affected Projects

SpeckleAdmin

Reproduction Steps & System Config (win, osx, web, etc.)

Proposed Solution (if any)

Step 0:

• I've read the contribution guidelines!

There is no progress indication on whether anything is happening!

Step 0:

• I've read the contribution guidelines!

(I've not posted an issue here before, so apologies if this is in the wrong place or anything)

Expected Behaviour

For a stream created manually in Hestia, there are four tabs across the top that let you see Overview, Sharing, Edit Data, and History. Your team members can go to the Edit Data tab and view the string/number data there in the UI.

Actual Behaviour

I can send and receive the data in Dynamo, but there's no Data button in the UI for another team member to go look at the data I've sent to the stream. The data can also be viewed using the API url or by adding /data to the UI URL

Affected Projects

Don't think so; it's really not a huge problem since the data is still sent. It's just a little awkward for other team members to view the data in the UI if they're unfamiliar.

Reproduction Steps & System Config (win, osx, web, etc.)

Create a stream and send string/number data to it using the Speckle Sender in Dynamo then view it in the UI frontend.

Proposed Solution (if any)

I imagine having a button for 'Data' in the menu so others can view the data even if they don't have permission to edit would be sufficient.

Step 0:

• I've read the contribution guidelines!

In here we should be passing as well the &token=${mytoken} or however the syntax was. Do refer to actually #46 re @logan12358 's comment about sockets - the whole mechanism should be offloaded and handled centrally, as we don't need to open new ones for each connection (should have one client id per session and join/leave rooms as necessary & update store accordingly).

Step 0:

• I've read the contribution guidelines!

Line based objects are not visible in the normal view (dark mode is fine). Originally reported by @Jeast85. See:

Title says it all

I have found people I have added to a project, cannot add streams to the project.

When accessing a speckle app served by a server (from the /plugins), there is no default url present which is weird - it should use that one by default.

Flow could be on the lines of: check if url is app.speckle.systems, if yes - no default url. if it's a different url, assume it's an app served by the server and add the root url as default.

This could lead to confusion, so maybe better not changing the case...

Step 0:

• I've read the contribution guidelines!

Expected Behaviour

When I send someone a link to speckle viewer with a particular stream displayed (e.g. https://hestia.speckle.works/#/view/NDpZHyAWc) they should be able to open in a browser and see the building model.

Actual Behaviour

If the user has never logged into the speckle server before, they see a blank speckle viewer with no model selected.

Affected Projects

¯_(ツ)_/¯

Reproduction Steps & System Config (win, osx, web, etc.)

Open an incognito window (clearing cookies would presumably have the same effect) in chrome, go here => https://hestia.speckle.works/#/view/NDpZHyAWc

Proposed Solution (if any)

¯_(ツ)_/¯ I never noticed this in the past.. Maybe roll back whatever caused it?

Step 0:

• I've read the contribution guidelines!

Expected Behaviour

I should be able to read everything in the right hand tool panel in speckle viewer.

Actual Behaviour

When I open the dropdowns, especially the stream selector dropdown, the names are usually cut off due to the width of the panel. the fine print under the stream name is always cut off.

E.g.

Affected Projects

Nada, its just kinda annoying if you want to see the date something was uploaded while selecting a stream in the viewer.

Reproduction Steps & System Config (win, osx, web, etc.)

open viewer, try to select a stream to view

Proposed Solution (if any)

Create width controller or at least just format that fine print so ID is on one line and date uploaded is on another.

Step 0:

• I've read the contribution guidelines!

Expected Behaviour

There should be an option in the viewer to automatically refresh streams, rather than the current manual-only button in ViewerLoadedStreamsCard.vue. This could be a checkbox on the card, which determines whether auto-refresh is enabled for each stream. There could also be a global checkbox to enable/disable all auto-refresh (related to #45).

Actual Behaviour

Currently, there's only a manual refresh button.

Proposed Solution (if any)

There probably ought to be something stored alongside each stream to identify whether to auto-refresh or not. The websocket handler probably belongs nearer to the store than to ViewerLoadedStreamsCard.
There might be complications to be wary of around selections and filters.

Step 0:

• I've read the contribution guidelines!

Context: slowly move away from server-side installed plugins to single-point of contact web-uis that can connect to one/more servers (similar to slack workspaces).

Reason:

• easier CI-CD (do it once, rather then on a per-server basis)
• keeps user updated with latest bug fixes
• no need for an ui that manages plugin updates on the server

Actual Behaviour

Because of the federated nature of speckle, you can use the admin ui to connect to multiple servers (see them as slack workspaces). Consequently, when sharing a link, we need to track the server that we're drawing the data from too.

Currently, the app assumes the server lies at ${rootUrl}/api, which creates headaches when sharing things from app.speckle.systems (netlify cicd), or potentially any other ci-cd'ed instance of it.

Affected Projects

For now just this one.

Proposed Solution (if any)

Append the current server's uri to all links; always check the server url on mounted and set it.

See if we can do this automagically via the router; otherwise we'll need to figure out a different way.

This might spell a bigger architectural change for the admin interface.

Step 0:

• I've read the contribution guidelines!

Add a css2d renderer where to be able to display annotations:

• labels
• text
• dimensions?

Step 0:

• I've read the contribution guidelines!

Expected Behaviour

• A new "rotate" button near the project title that loads all the streams at once into the viewer;
• also the ability to search and select a project in the stream search panel, or a new "search project" panel

Actual Behaviour

Users have to manually add all the project streams for a global view

Affected Projects

none (AFAIK)