-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[PLAY-845] Add swift to kits page #2778
Conversation
🎉 Congratulations on creating an Alpha Version! Your Alpha for Ruby Gems is 13.9.0.pre.alpha.play845addswiftkitspage1272 Your Alpha for NPM is 13.9.0-alpha.play845addswiftkitspage1272 |
🎉 Congratulations on creating an Alpha Version! Your Alpha for Ruby Gems is 13.9.0.pre.alpha.play845addswiftkitspage1273 Your Alpha for NPM is 13.9.0-alpha.play845addswiftkitspage1273 |
🎉 Congratulations on creating an Alpha Version! Your Alpha for Ruby Gems is 13.10.0.pre.alpha.play845addswiftkitspage1332 Your Alpha for NPM is 13.10.0-alpha.play845addswiftkitspage1332 |
playbook-website/app/components/playbook/pb_docs/kit_example.html.erb
Outdated
Show resolved
Hide resolved
**What does this PR do?** A clear and concise description with your runway ticket url. https://nitroqa.powerhrg.com/dev_docs/playbook Bug shipped in #2778
**What does this PR do?** A clear and concise description with your runway ticket url. [A recent PR broke sandpack experimental feature](#2778) This is an interim fix to check for missing variable def. A follow-up story should be created to fix the underlying missing `type` variable. cc: @nidaqg @jasperfurniss **Screenshots:** Screenshots to visualize your addition/change N/A #### Checklist: - [x] **LABELS** Add a label: `enhancement`, `bug`, `improvement`, `new kit`, `deprecated`, or `breaking`. See [Changelog & Labels](https://github.com/powerhome/playbook/wiki/Changelog-&-Labels) for details. - [x] **DEPLOY** I have added the `milano` label to show I'm ready for a review. - [ ] **TESTS** I have added test coverage to my code.
What does this PR do? A clear and concise description with your runway ticket url.
Inspired by #2756
We are adding a swift section to our docs website.
Swift docs do not have "example" files as our example docs run
erb
orjsx
files and use that file extension to identify a file as an "example" file.md
files are for the description of the documentBecause all swift docs are
md
files I added a bunch of conditional logic that checks for_swift
in themd
file to consider it a sudo swift exampleHow to test? Steps to confirm the desired behavior:
Checklist:
enhancement
,bug
,improvement
,new kit
,deprecated
, orbreaking
. See Changelog & Labels for details.milano
label to show I'm ready for a review.