Adding a page per `packs` documentation on
https://github.com/rubyatscale/packs
`packs` is a system to modualize ruby projects.
---------
Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
I was looking for notes and then when i was searching svelte i couldn't
see the possible search hits.so i turned autocomplete off now it works
like charm.
Fixes missing code highlighting in half of the Python code snippets.
The top half of the page had code examples formatted as code blocks with
4 space character indentations and no syntax highlighting as a result.
The bottom half on the other hand, used code blocks surrounded by
"```py" formatting brackets which hints to many markdown renders that
syntax highlighting should be applied.
This unifies the code blocks in the top half of the page to use the same
formatting syntax used in the bottom half with syntax highlighting.
This change was prompted by requests to add the syntax highlighting in
comments on the https://devhints.io/python page.
A warning is added to the polyfill.io sheet in relation to the malicious
script that is now being served by polyfill.io. Removed all links to
that domain.
The code snippets have also been updated to use Cloudflare's script
instead. This allows users to keep using polyfill securely while they
move their codebase away from using this polyfill.
Cloudflare press release:
https://blog.cloudflare.com/polyfill-io-now-available-on-cdnjs-reduce-your-supply-chain-riskFixes#2145
---------
Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
Previous link for the Go wiki was no longer valid. Updated to the
current wiki site location.
Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
The above case is a new Bad case added by https://github.com/rstacruz/cheatsheets/pull/1798 . It is designated as Bad due to performance issues, but it is not actually a Negative example. In practice, the following would be the same test:
```ruby
expect(page).to have_button('Save')
!expect(page).to have_button('Save')
```
This is not an example that will appear on the capybara cheat sheet, because it is a problem with how RSpec is written. I think it should be removed because it creates confusion.
* fixed conditional equal operator as per the official documentation https://fishshell.com/docs/current/cmds/test.html
* updated docker compose cheatsheet, added good to remember functionalities and added V2 mention
---------
Co-authored-by: yassin <yassin.bousaadi@sword-group.com>
