🥔✨ `Gizmos` #709

zspencer · 2022-06-09T01:55:31Z

#709 When we were smoke-testing the Marketplace, I realized we had to destroy and re-create the Marketplace, but the way we delete them was... uhhh not respecting the (very prudent) foreign-keys we had added! So now FurniturePlacements polymorph into their child implementation prior to destruction, so that all `dependent: :destroy` etc. actions get carried out. Co-authored-by: Dalton <[email protected]>

- Extracted from: #1083 - #74 - #709

🧹 `Furniture`: use `location` rather when building new Furniture - Extracted from: #1083 - #74 - #709

- #709 This helps prepare us to rename from `FurniturePlacement` down to `Furniture` by getting rid of some unnecessary fiddly bits. Theoretically, our next step is to inline the `Furniture` namespace into `FurniturePlacement` to make space at the `Furniture` namespace; then rename `FurniturePlacement` to `Furniture`... And then we don't have `Placement` anymore! Just `Furniture`!

…lacement` (#1208) * 🧹 `Furniture`: Streamline routing & instantiation - #709 This helps prepare us to rename from `FurniturePlacement` down to `Furniture` by getting rid of some unnecessary fiddly bits. Theoretically, our next step is to inline the `Furniture` namespace into `FurniturePlacement` to make space at the `Furniture` namespace; then rename `FurniturePlacement` to `Furniture`... And then we don't have `Placement` anymore! Just `Furniture`! * `Furniture`: Inline `Furniture` into `FurniturePlacement` This gets us almost all the way to the rename; since we don't have the `Furniture` namespace in the way... * 🧹 `Furniture`: Dynamic registry to get around circular class-load dependency So: ```app/furniture/form.rb class Form < FurniturePlacement end ``` loads ```app/models/furniture_placement.rb class FurniturePlacement REGISTRY = { Form } end ``` Which loads... You guessed it! ```app/furniture/form.rb class Form < FurniturePlacement end ``` Pulling the registry definition out of interpret-time and into runtime fixes that; since the `Form` constant isn't referenced until the `FurniturePlacement.registry` method is accessed.

- #1209 (comment) - #709 I don't really like the direction this pushes specs, but I can live with it. In particular, a single assert per request/response seems... excruciatingly slow. But there are other mechanisms we can explore to mitigate that as it gets out of hand.

- #832 - #1155 - #1154 - #709 As I was working to onboard Piikup, I discovered I couldn't really write an easy script to merge into a space since I didn't have the associations together. Now they're super tight! Yyyaaaaaaah!

- #1187 - #709 Apparenltly our tailwind config wasn't detecting classes in furniture's `_component.rb` files. Womp. Womp.

- #831 - #709 There's something appealing about switching to Rails' built in `Single Table Inheritance` for `Furniture`, rather than our flyweight registry; but I also know that STI can be a bit of a smell... Anyway, now when you call `Marketplace.all` and get *only* `Marketplace`s. Maybe someday we'll pull this up in to the `Furniture` classes responsibilities so we don't have to do it on every single piece of Furniture...

- #709 Sprouts a tiny Gizmo for linking to Sections. At some point, we'll want to add a UI for picking which `Sections` to include, preferably an `AllowList` so that adding a `Section` doesn't immediately publish it.

- #709 - zinc-collective#1 This is an attempt at using a README as a form of product-design documentation. It follows the Pain-Dream-Fix recipe for marketing copy, with an emphasis on the code's *purpose*. By exposing the purpose of the code; new contributors (or contributors that have been away for a bit) have a way of grounding themselves in the product-thinking behind the project itself. That said, good README's have additional context beyond the purpose, such as: - A Data Model, which exposes a high-level view of the interactions between entities within the system we are building. - Setup instructions, such as guidance for how to populate an initial database or a reference to additional software to install. But for now we don't have either of those things; and I wanted to do some Product-based House Keeping, such as creating Fauxsonas and Use Cases before diving into Engineering.

- zinc-collective#709 - #1 This is an attempt at using a README as a form of product-design documentation. It follows the Pain-Dream-Fix recipe for marketing copy, with an emphasis on the code's *purpose*. By exposing the purpose of the code; new contributors (or contributors that have been away for a bit) have a way of grounding themselves in the product-thinking behind the project itself. That said, good README's have additional context beyond the purpose, such as: - A Data Model, which exposes a high-level view of the interactions between entities within the system we are building. - Setup instructions, such as guidance for how to populate an initial database or a reference to additional software to install. But for now we don't have either of those things; and I wanted to do some Product-based House Keeping, such as creating Fauxsonas and Use Cases before diving into Engineering.

* 📝 `TOBIAS`: Sprout README as Contributor-Facing Product Marketing - zinc-collective#709 - #1 This is an attempt at using a README as a form of product-design documentation. It follows the Pain-Dream-Fix recipe for marketing copy, with an emphasis on the code's *purpose*. By exposing the purpose of the code; new contributors (or contributors that have been away for a bit) have a way of grounding themselves in the product-thinking behind the project itself. That said, good README's have additional context beyond the purpose, such as: - A Data Model, which exposes a high-level view of the interactions between entities within the system we are building. - Setup instructions, such as guidance for how to populate an initial database or a reference to additional software to install. But for now we don't have either of those things; and I wanted to do some Product-based House Keeping, such as creating Fauxsonas and Use Cases before diving into Engineering.

- #709 We initialize `active-storage` and `aws-sdk-s3` when we load the application code, which loads up `config/storage.yml` and sets up an AWS S3 Client. But the `Journal` doesn't use AWS S3 (yet?), so the continuous integration environment doesn't have AWS credentials. Which causes [build failures]. I *could* add credentials to the Journal Gizmo's CI environment, but that would mean other Gizmos that don't use AWS S3 would need AWS credentials So I'm going to add some fake test credentials to the .env.test.example file, which should let the AWS S3 client initialize and then explode horribly when we try and shovel some data into it. [build failures]: https://github.com/zinc-collective/convene-journal/actions/runs/7690936384/job/20955491503

- #1 - zinc-collective#709 - For a #9 to leverage the behavior we described, we need a way to put tobias on the web. zinc-collective#709 are the equivalent of an "App" in the Convene world. - Note: `Gizmo` and `Furniture` are equivalent. We probably should finish zinc-collective#1472 - The migration change makes sure that ahttps://github.com//issues/4 is connected to #1

- #709 - #2200 (review) Markdown is cool, but it's nerd-forward. ActionText is a much more human-friendly way of implementing rich text in Rails applications. I don't know enough about [Trix] to know if it will work in multi-user contexts; or how it will work with rich-embeds, ala Notion or Google Docs But I think it's a good-enough-default for now; and if we get to the point where embeddables or multi-user editing of a field is important we can figure that out. [Trix]: https://trix-editor.org/

- #709 - #2200 (review) - #2211 Markdown is cool, but it's nerd-forward. ActionText is a much more human-friendly way of implementing rich text in Rails applications. I don't know enough about [Trix] to know if it will work in multi-user contexts; or how it will work with rich-embeds, ala Notion or Google Docs But I think it's a good-enough-default for now; and if we get to the point where embeddables or multi-user editing of a field is important we can figure that out. [Trix]: https://trix-editor.org/

- #1 - zinc-collective#709 - For a #9 to leverage the behavior we described, we need a way to put tobias on the web. zinc-collective#709 are the equivalent of an "App" in the Convene world. - Note: `Gizmo` and `Furniture` are equivalent. We probably should finish zinc-collective#1472 - The migration change makes sure that ahttps://github.com//issues/4 is connected to #1

- zinc-collective#709 - zinc-collective#2200 (review) - zinc-collective#2211 Markdown is cool, but it's nerd-forward. ActionText is a much more human-friendly way of implementing rich text in Rails applications. I don't know enough about [Trix] to know if it will work in multi-user contexts; or how it will work with rich-embeds, ala Notion or Google Docs But I think it's a good-enough-default for now; and if we get to the point where embeddables or multi-user editing of a field is important we can figure that out. [Trix]: https://trix-editor.org/

- #1 - zinc-collective#709 - For a #9 to leverage the behavior we described, we need a way to put tobias on the web. zinc-collective#709 are the equivalent of an "App" in the Convene world. - Note: `Gizmo` and `Furniture` are equivalent. We probably should finish zinc-collective#1472 - The migration change makes sure that ahttps://github.com//issues/4 is connected to #1

rosschapman · 2024-11-02T18:07:39Z

🧹 Relegated to cold storage.

zspencer added this to the 1.0 - Andromeda milestone Jun 26, 2022

zspencer mentioned this issue Jan 26, 2023

Furniture: Destroying a Furniture respects dependent: settings #1074

Merged

zspencer changed the title ~~Feature: Furniture~~ 🌱 Furniture Feb 26, 2023

zspencer changed the title ~~🌱 Furniture~~ 🌱🥔 Furniture Feb 26, 2023

zspencer mentioned this issue Mar 2, 2023

⛰️✨ Sections #1155

Closed

8 tasks

zspencer added a commit that referenced this issue Mar 3, 2023

🧹 Furniture: use location rather when building new Furniture

0a6212e

- Extracted from: #1083 - #74 - #709

zspencer mentioned this issue Mar 4, 2023

🧹 Furniture: use FurniturePlacement#location in forms #1180

Merged

zspencer added a commit that referenced this issue Mar 4, 2023

🧹 Furniture: use FurniturePlacement#location in forms (#1180)

d68323e

🧹 `Furniture`: use `location` rather when building new Furniture - Extracted from: #1083 - #74 - #709

This was referenced Mar 11, 2023

🧹 Furniture: Consolidate to Furniture to prep to drop FurniturePlacement #1208

Merged

🧹 Furniture: Complete the rename! #1209

Merged

zspencer mentioned this issue Mar 11, 2023

🧹 Furniture: Appease the Fuzz #1211

Merged

zspencer mentioned this issue Mar 31, 2023

🧹 Space, Furniture, and Room: Fill in missing associations #1285

Merged

zspencer added a commit that referenced this issue Apr 10, 2023

🛠️ Components: Tailwind Look for classes in Furniture

10ced3c

- #1187 - #709 Apparenltly our tailwind config wasn't detecting classes in furniture's `_component.rb` files. Womp. Womp.

zspencer mentioned this issue Apr 10, 2023

🛠️ Components: Tailwind Look for classes in Furniture #1341

Merged

zspencer added a commit that referenced this issue Apr 10, 2023

🛠️ Components: Tailwind Look for classes in Furniture (#1341)

8ca3bdf

- #1187 - #709 Apparenltly our tailwind config wasn't detecting classes in furniture's `_component.rb` files. Womp. Womp.

zspencer mentioned this issue Apr 30, 2023

🧹🛠️ Marketplace: return only Marketplaces! #1423

Merged

zspencer modified the milestones: 1.0 - Andromeda, 1.1 - Andromeda I May 4, 2023

This was referenced Nov 24, 2023

✨ Gizmo: SectionNavigation #1964

Merged

🌸 DesignLibrary #1187

Open

zspencer mentioned this issue Dec 11, 2023

🐞 Sections: Destroying a Section with Gizmos fails horribly #2019

Closed

zspencer mentioned this issue Jan 8, 2024

🌱🗜️✨ TOBIAS: TOpical Basic Income Administration System zinc-collective/tobias#1

Open

16 tasks

zspencer mentioned this issue Jan 8, 2024

📝 TOBIAS: Sprout README as Contributor-Facing Product Marketing zinc-collective/tobias#2

Merged

zspencer mentioned this issue Jan 25, 2024

🌫️🗜️ Gizmo: WebRing #2150

Open

zspencer mentioned this issue Jan 29, 2024

🛠️ Gizmos: Gizmos that don't use S3 shouldn't fail w/o AWS #2160

Merged

zspencer mentioned this issue Feb 13, 2024

✨ Tobias: Expose Trust#show with link to Payout#new zinc-collective/tobias#23

Open

zspencer mentioned this issue Feb 16, 2024

⚙️ Gizmos: Support ActionText #2211

Merged

rosschapman closed this as completed Nov 2, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

🥔✨ `Gizmos` #709

🥔✨ `Gizmos` #709

zspencer commented Jun 9, 2022 •

edited

Loading

rosschapman commented Nov 2, 2024

🥔✨ Gizmos #709

🥔✨ Gizmos #709

Comments

zspencer commented Jun 9, 2022 • edited Loading

Potatoes

Sprouts

Unplanted

Use Cases

For Developers

Bugs

rosschapman commented Nov 2, 2024

🥔✨ `Gizmos` #709

🥔✨ `Gizmos` #709

zspencer commented Jun 9, 2022 •

edited

Loading