Structured data for store/organisation#6
Structured data for store/organisation#6rahulsingh321 wants to merge 13 commits intogms-electronics:mainfrom
Conversation
|
@rahulsingh321 translations for labels are entirely missing. |
|
Todos: |
|
@kennyadsl we are unsure if using addresses or just make columns here. Specs by google are following:
|
3a5dad4 to
0ad8199
Compare
|
@rahulsingh321 |
|
@rahulsingh321 wait for PR description by me before making pr |
|
@rahulsingh321 please update the screenshot |
bb18ebd to
c31ef6d
Compare
fthobe
left a comment
There was a problem hiding this comment.
Generally it looks good, some minor things:
- try to align the section headers with what they do in the new admin
- try to be more consistent with naming throughout a PR
Rest looks good, form is well structured, tests are there. I don't see why this wouldn't be ok. @shahmayur001 needs to remove the wrongly placed commits from here.
core/db/migrate/20250202173007_add_store_attributes_to_spree_stores.rb
Outdated
Show resolved
Hide resolved
2bdf3fd to
5221825
Compare
5221825 to
4d128b4
Compare
4d128b4 to
747e3ab
Compare
747e3ab to
5ca04d7
Compare
c84b99e to
bbff7bc
Compare
This event fires when the order `#cancel!` event is fired as part of the stock order state machine events. Co-Authored-By: Adam Mueller <adam@super.gd>
This event fires when `OrderCancellations#short_ship` is fired when an an inventory unit is canceled from an order. Co-Authored-By: Adam Mueller <adam@super.gd>
This adds a `:carton_shipped` event that is published whenever `OrderShipping#ship` succeeds to mark a carton as shipped. Co-Authored-By: Adam Mueller <adam@super.gd>
Add new order events
d9c8bdd to
28bd919
Compare
The comment was inconsistent with the default setting. No functional changes have been made.
…onfig [Docs] Fix Meta Data Restriction Comment to reflect default setting
This PR fixes an HTML structure break caused by an unclosed form_tag, ensuring that forms added after using ui/table are rendered correctly.
## Background
While customizing the index page to add a new form, I encountered a problem where the added form was not displayed in the browser. Upon investigation, I discovered that the issue stemmed from the form_tag in ui/table/component.html.erb not being explicitly closed, which resulted in subsequent form tags disappearing.
``` rb
<%= render component("ui/table/toolbar").new("data-#{stimulus_id}-target": "batchToolbar", role: "toolbar", "aria-label": t(".batch_actions"), hidden: true) do %>
<%= form_tag '', id: batch_actions_form_id %>
<% @data.batch_actions.each do |batch_action| %>
<%= render_batch_action_button(batch_action) %>
<% end %>
<% end %>
```
Due to the lack of a proper block structure closing the form_tag, the HTML became malformed, and any form tags declared afterward were not rendered.
Updated the form_tag to use a block form, ensuring that the opening and closing tags are explicitly defined.
76b10b9 to
a7fa008
Compare
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/textarea In HTML, the initial content of a <textarea> is specified between its opening and closing tags, not as a `value` attribute. Therefore we must set `content`, rather than passing `value` for text areas.
Fix ui/forms/input component for tag: :textarea
a7fa008 to
fc8e744
Compare
…in_admin_table_component [Admin] Fix Unclosed form_tag in table component
…-actions-permission Revert "GH: Allow backport workflow to trigger actions"
This Commit provides the possibility to store legal information in the store resource. Given the wide array of different information required by country, the information stored here provides a baseline for most countries, but might need to be augmented in some jurisdictions. This commit is not meant as legal advisory. Inform yourself about eventual requirements in your country of operation. Some additional information that might be needed: - Legal Representative, - Share Capital of the company, - Contacts for privacy. Schema.org has a schema to markup organizations that has been widely adopted by various search engines: | | https://schema.org/Organization Support / Docs | |--------|-----------------------------------------------------------------------------------| | Bing | https://www.bing.com/webmasters/help/?topicid=cc507c09 | | Google | https://developers.google.com/search/docs/appearance/structured-data/organization | | Yandex | https://yandex.com/support/webmaster/schema-org/what-is-schema-org.html | This update allows to return all organization data on frontend via jsonb if implemented according to schema documentation on a per store basis and edit the data via API and Backend (Old / New). The implemented fields are: - legal_name, - contact_email, - contact_phone, - vat_id, - tax_id, - address1, - address2, - Zip code and city, - state_name, - country_id, - and state_id. Some additional notes regarding the size of the commit: While this commit seems massive in size, no functionality has been added apart from storing the values, no logical changes have been made, hence the commit while bigger in size is simple to analyse. Apart from testing routines, this commit does not contain functional code. Where possible the structure of current address forms has been adopted. Fixes solidusio#6173
fc8e744 to
a1b1502
Compare
|
@kennyadsl should be good to go. |
|
@kennyadsl could you check again? |
Store form UI:
