* add series to dashboard sidebar template
* add series view to the user dashboard
* update typo
* merge master
* modify the dashboard to hold series count that link to the user's series page
* remove schema unnecessary change
* remove controller count from function
* Add ProfileField model
* Fix schema.rb
* Add service objects for base and link fields
* feat: show an index of profile fields and allow them to be edited
* Fix schema.rb
* Add service objects for base and link fields
* Add link fields to seeds
* Make placeholder a keyword argument
* Add work fields
* Add explanation column to profile fields
* Add coding fields
* Switch from inheritance to mixin
* Add email checkbox to base fields
* Add branding fields
* Add spec for ProfileFields::FieldDefinition
* chore: moved the migration file
* feat: add a create and destroy route
* feat: render a partial form
* fix: oops form instead of f
* Move migration back into correct location
* Rename column from explanation to description
* Rename attribute in mixin
* chore: update classed for buttons
* chore: rename from explanation to description
* chore: explanation to description
* chore: new profie field
* fix: only one submit button per form
* fix: update the form
* fix: remove files that got merged mistakenly
* chore: finally, some specs...
Co-authored-by: Michael Kohl <citizen428@dev.to>
* Rename FastlyHeaders to CachingHeaders, conditionally experiment with removing no-cache
We suspect that it is safe to remove `no-cache` entirely from the Cache-Control headers that are sent
along to Fastly, but there is no great way to confirm this hypothesis. We're testing this by experimenting
on one single article. We will conditionally default to the same headers that we send to Nginx, and send
those headers to Fastly (by removing `no-cache` and adding in `max-age`, which should be ignored since Fastly
also has Surrogate-Control headers added to it, which include a `max-age`, which Fastly should prioritize
over any other `max-age`.
Once we've confirmed that this doesn't cause issues on the Fastly side, we can remove this check and use
the same Cache-Control headers for both Fastly and Nginx.
* Add check for request.env[REQUEST_PATH].present?
* Fix schema.rb
* Add service objects for base and link fields
* Add link fields to seeds
* Make placeholder a keyword argument
* Add work fields
* Add explanation column to profile fields
* Add coding fields
* Switch from inheritance to mixin
* Add email checkbox to base fields
* Add branding fields
* Add spec for ProfileFields::FieldDefinition
* Move migration back into correct location
* Rename column from explanation to description
* Rename attribute in mixin
* chore: rename from explanation to description
* Add ProfileFields::ImportFromCsv
* Simplify ProfileFields::ImportFromCsv
* Add comment about disabled cop to spec
* Add TODO comment to Rake task
* Document mixin
* Add groups to profile fields
Co-authored-by: Ridhwana <ridhwana.khan16@gmail.com>
This PR moves the away from the dev specific naming to forem w/r/t container
things. Also moves to the Forem quay.io org.
* Move to Forem from DEV
* Add in assets and packs directories.
* flare tag line height
* .
* dropdown fix + actions bar fix
* actions bar on mob
* .
* css commented out
* .
* button fix
* preload adjustments
* tags
* Fixed listings modal to make it semantic HTML via <dialog />.
* Refactor an a11y fix.
* Removed test that is no longer needed.
* Added missing global function for test..
* Fixed broken <ListingFiltersCategories /> tests.
* Refactor of mobile dropdown for listing categories.
* Updated a TODO.
* Made the clear query button a crayons Preact button.
* padding
* Fixed listings modal for accessiblilty.
* Removed rspecs that are no longer valid.
* We're no longer using the <dialog /> element, at least for now, so CSS changes aren't necessary.
* Wasn't supposed to be committed.
Co-authored-by: Nick Taylor <nick@dev.to>
Co-authored-by: rhymes <rhymes@hey.com>
Co-authored-by: Nick Taylor <nick@iamdeveloper.com>
* Feature 🚀 : Ability to delete messages in chat channels
- Sending message ID to frontend
- Deleting Message
- Use pusher to delete message realtime
* Minor Bug 🐞: Show message action only for current user
- User can delete or edit their own messages
* Test cases added
* Bug 🐞: Update message id for receiver
Message id was not sent to receiver by pusher
* Refactoring🛠: Message controller refactoring
* Test Cases📝 : Specs for Delete message added
* Feature 🚀 : Ability to edit messages
* Test Cases📝 : Specs for Edit message added
* Merge conflict resolved
* 🐞 Fixes bug #9503 When joining a new room, user is not taken to the new room
Co-authored-by: Narender Singh <narender2031@gmail.com>
* update wsl installation information
* update postgreSQL installation for windows to wsl2
* update elasticsearch instructions for wsl2
* Update imagemagick installation for wsl2
* implement suggestions
- fix typo
- provide elasticsearch install commands rathen than links
- switch wsl steps to numbered
* Move from OpenStruct to Struct in Organization
* Add data update script
* Introduce Articles::CachedEntity model
* Update data update script for new model
* Fix comment
* Update jbuilder
