chore(widget): rename file and add type hint)

packages/widget/src/detail-view.ts

@@ -17,7 +17,7 @@ export function renderDetailsView(
   allNodes: DisplayObject[],
   updateSelectedNode: (node: DisplayObject) => void,
   closeDetailsView: () => void,
-) {
+): HTMLTemplateResult {
   const opts = TYPE_DISPLAY_OPTIONS[selectedNode.type];
   const backgroundColor = opts.detailViewBackgroundColor || opts.backgroundColor;
   const textColor = opts.detailViewTextColor || opts.textColor;

packages/widget/src/util.ts → packages/widget/src/display-object.ts

@@ -15,6 +15,13 @@ export interface DisplayObjectMetadata {
   actors?: string;
 }
 
+// DisplayObjects are the widget's internal representation of a node from the graph view.
+// They roughly correspond to a ThingT in the Docmap spec, but with only the fields that we want to display.
+export interface DisplayObject extends DisplayObjectMetadata {
+  nodeId: string; // Used internally to construct graph relationships, never rendered
+  type: string;
+}
+
 // The following 3 statements allow us to use FieldsToDisplay both as a type and as something we can
 // check against at runtime. We could also use io-ts for this, but that felt like overkill since this
 // is the only place in the widget where we do something like this.
@@ -32,13 +39,6 @@ export function isDisplayObjectMetadataField(key: string): key is DisplayObjectM
   return key in DisplayObjectMetadataPrototype;
 }
 
-// DisplayObjects are the widget's internal representation of a node from the graph view.
-// They roughly correspond to a ThingT in the Docmap spec, but with only the fields that we want to display.
-export interface DisplayObject extends DisplayObjectMetadata {
-  nodeId: string; // Used internally to construct graph relationships, never rendered
-  type: string;
-}
-
 // Returns a new DisplayObject which has no fields set to the value undefined,
 // meaning the new Display Object can be merged with another DisplayObject via destructuring.
 //