Contained within this charter is an outline of expectations and guidelines for members of the frontend team. This is an open, collaborative document.
Pull request #11789 updated | |
19:46:40 Connecting to https://api.github.com using github-token | |
Obtained ci/TestJenkinsfile from 763ca504b0341a063692334aafba2e14d570c475+8cddda12c259d3de97046d9b168e98cf8f186212 (84de0ba1c910b946c052ac9beaf08d11aa7db2d8) | |
Loading library siloSharedLibs@add-set-e2e-test-tag | |
Examining silo-technologies/jenkins-libraries | |
Attempting to resolve add-set-e2e-test-tag as a branch | |
Resolved add-set-e2e-test-tag as branch add-set-e2e-test-tag at revision 65e3554fc23b25132d7997b15afa5f39344d050f | |
The recommended git tool is: NONE | |
using credential github-token | |
> git rev-parse --resolve-git-dir /var/jenkins-home/workspace/ontend_end-to-end-tests_PR-11789@libs/8c3787349159e7f293afd53f26cd251c154ae580288387536bd74f1ca2cfcf8d/.git # timeout=10 |
Goes over the issues with using flex box to align inline elements vs block elements
When table cells for header and body content utilize the flex box, they commonly use justify-content: flex-end
for aligning items to the right.
There's nothing inherently wrong with this method, as it behaves as expected when aligning block-level elements.
<form action="/cart/add" method="post"> | |
{% if product.variants.size > 1 %} | |
{% if product.options[0] %} | |
{% assign used = '' %} | |
<label for="select-one">{{ product.options[0] }}</label> | |
<select id='select-one' onchange="letsDoThis()"> | |
{% for variant in product.variants %} | |
{% unless used contains variant.option1 %} | |
<option value="{{ variant.option1 }}">{{ variant.option1 }}</option> | |
{% capture used %}{{ used }} {{ variant.option1 }}{% endcapture %} |
ReCharge supports the usage of a special, expiring token as a way to strengthen a customer's account security.
When a user signs in to manage their account, a token will be generated, assigned to their account, and appened to the URL. This token will be used while they navigate through pages and make requests. If an attempt is made to access an account without either a token or using an unauthorized-token, the request will be denied and a redirect will occur to the login/token request page.
ReCharge will handle generating a token, emailing it, and verifying authorized tokens against the customer account. It will even perform redirects if an incorrect token is used.
[ | |
{ | |
handle: 'bricks', | |
id: 10792964429, | |
subscription_only: false, | |
variant_to_duplicate: { | |
44870735309: 20287304007739, |
From fixing bugs to refactoring pages or even building brand new features, the developer resources outlined below will be helpful for anyone looking to work with the ReCharge codebase.
*ANNOUNCEMENTS:* Deployed changes | |
*ACTION: file or function - action description* | |
For a description of the changes, please see previous "Upcoming changes" announcement |
*ANNOUNCEMENTS:* Upcoming changes | |
*ACTION: file or function - action description* | |
`Who does this affect?` | |
Brief description | |
`Does this affect current stores?` |
- Upgrade Stripe JS api from v2 to v3
https://js.stripe.com/v3/
- Add Stripe Element
- ``