Visual language#38
Closed
dibaunaumh wants to merge 109 commits into
Closed
Conversation
…address. Also reduced distance from speaker 10->2
… dev using downloaded image
…ootprint. this is tech-debt - proper solution is to remove chat to its own storage & pull just the latest
Initiatives as tables
Stage data
…e caller already does that using an additional query
Include parent option added to DAL
…se fields. This used to work long time ago, but got broken
Api fixes for provisioning users
Register/unregister endpoints store callback_urls per battery_type in Redis sets. The chat dispatcher now looks up battery bldgs on the message floor, resolves their types to registered callbacks via Redis, and picks one randomly to dispatch each message. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
… the validation requiring flr & flr_url
…ge (not the cleanest, but have to get this working). Also added an endpoint to get a bldg by the bldg_url
Multi tenant batteries
… how redis is used for transient data). Not sure it's the right approach though, because I want to keep the principle of , so not store data in a db hidden from the user, but rather store everything - including staging data - in bldgs, which the user can see
…staging-data Expend usage of graph db for staging data
Container bldgs now have a visual_language jsonb column that maps semantic entity types to 3d_object names and floor height metadata. This decouples what a bldg represents (entity_type) from how it looks when rendered. - New migration adding visual_language column to bldgs table - Default visual language with all 40 built-in entity type mappings - Refactored add_composite_bldg_metadata from 10+ hardcoded clauses to a single lookup against the visual language map - BldgView returns visual_language as JSON-encoded string - test.exs now reads DB_USER from env (consistent with dev.exs) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Added Buildings.is_authorized_owner?/2 that walks up the container chain to check if the given email owns the building or any of its ancestors. This means if you own a building, you can create, move, connect, and manage everything nested inside it. Replaced all 6 inline Enum.find ownership checks in BldgCommandExecutor with the new function. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The bldg_url hierarchy alternates between buildings and floors (e.g., g/udi-bauman/l0/goal_name). When walking up to check ancestor ownership, floor URLs like "g/udi-bauman/l0" aren't in the bldgs table, so the lookup returned nil and stopped the walk. Now continues walking up past floors until it reaches an actual building or the root. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.