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

New-UDTable creates unnamed endpoint #1257

Merged
merged 2 commits into from
Oct 15, 2019

Conversation

TonyBunce
Copy link
Contributor

Add a deterministic ID to the UDElement created by New-UDTable. Without this any UDTable will create an endpoint with a new random GUID every time the dashboard is restarted. That causes clients with their browser open during a dashboard restart to suddenly get 404 errors.

I used "$Id-tbody" as the ID of the endpoint but any value based on $Id should work.

Add a deterministic ID to the UDElement created by New-UDTable.  Without this any UDTable will create an endpoint with a new random GUID every time the dashboard is restarted.  That causes clients with their browser open during a dashboard restart to suddenly get 404 errors.
@adamdriscoll adamdriscoll added this to the 2.7.0 milestone Oct 15, 2019
@adamdriscoll adamdriscoll merged commit 31a0a29 into ironmansoftware:master Oct 15, 2019
@McAndersDK
Copy link
Contributor

Should this not just be $ID ?
I dont think any of others make a postfix?

@TonyBunce
Copy link
Contributor Author

That would create two HTML elements with the same ID, which is invalid and likely to break any JavaScript that depends on document.getElementById

@McAndersDK
Copy link
Contributor

Ah yeah I do see that. Well I would say that the new-udelement -tag "div" should have another Id.
only the element with the browser call should have the true Id.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants