Description

New snippet for returning a string shortened to a given length. with ... appended by default.

PR Type

• [x] Snippets, Tests & Tags (new snippets, updated snippets, re-tagging of snippets, added/updated tests)
• [ ] Tools, Scripts & Automation (anything related to files in the scripts folder, Gatsby, website, Travis CI or Netlify)
• [ ] General, Typos, Misc. & Meta (everything related to content, typos, general stuff and meta files in the repository - e.g. the issue template)
• [ ] Other (please specifiy in the description above)

Guidelines

• [x] I have read the guidelines in the CONTRIBUTING document.

Description

I've made a simple function that shortens a string to a given length and appends an optional string to show it's been shortened.

https://3v4l.org/II4aX

I've got the code snippet in a .md file but don't know how to test the build process.

https://github.com/StyxOfDynamite/30-seconds-of-php-code/blob/master/snippets/shorten.md

Hello, everyone! Our GitHub organization would love to have you as part of the team. You will, of course, retain all rights to your code and repository, write access and all the good stuff. The only thing that changes is that the 30-seconds team will be able to help more often with your project's needs and you will get to have access to all our communication channels.

If you are interested, please reply with the following:

• Main person(s) responsible for the repository after the transfer (i.e. team leaders, up to 3 people).
• Any other people who should be part of the organization as members of the PHP team.

If you have any questions and/or concerns, please feel free to ask me about them.

Description

As title, since we've changed the code snippets building process, some works are missed during Travis CI build.

As we look at the .travis.yml, it only has the code snippets building and it doesn't have any unit test works to validate these code snippet behaviors reliable and expected.

And it also misses the section of how-to test cases writing on CONTRIBUTING.md

IMHO, we should add this back and add contributing tips about unit test writing.

@sohelamin, and @Chalarangelo, please concern this at your available time.

And recommend current solution to accomplish this issue.

Thanks :).

As title, I think we can consider adding the Date section to learn about simple date manipulation in 30-seconds with PHP.

@sohelamin, what do you think about this?

function decapitalize($string, $upperRest = false) { return strtolower(substr($string, 0, 1)) . ($upperRest ? strtoupper(substr($string, 1) : substr($string, 1)); }

function decapitalize($string, $upperRest = false) { return strtolower(substr($string, 0, 1)) . ($upperRest ? strtoupper(substr($string, 1)) : substr($string, 1)); }

Adds array collapse function.

Description

PR Type

• [X] Snippets, Tests & Tags (new snippets, updated snippets, re-tagging of snippets, added/updated tests)
• [ ] Tools, Scripts & Automation (anything related to files in the scripts folder, Gatsby, website, Travis CI or Netlify)
• [ ] General, Typos, Misc. & Meta (everything related to content, typos, general stuff and meta files in the repository - e.g. the issue template)
• [ ] Other (please specifiy in the description above)

Guidelines

• [X] I have read the guidelines in the CONTRIBUTING document.

Hey there, @30-seconds/php team! How's it going?

As you might have noticed, we are migrating repositories toa new, unified structure and template to make it easier for the core teams to maintain them. I will outline below the list of changes we are thinking of making and you can pitch in and help us (me and @fejes713) figure out the best fit and timeline for this all:

• [ ] Update logo to match the style of the other repositories (@Chalarangelo)
• [ ] Update snippets to the new format and match quality standards (open)
• [ ] Remove leftover scripts, code, systems etc [1] (@fejes713)
• [ ] Copy systems, scripts, tools from 30-seconds/30-seconds-starter and configure accordingly (@fejes713)
• [ ] Update static parts, guidelines, issue/PR templates (@fejes713)
• [ ] Add Google Analytics, DNS records for php.30secondsofcode.org (@Chalarangelo)
• [ ] Rename to 30-seconds-of-php (all existing links are handled automagically by GitHub to point to the new name) (@Chalarangelo)
• [ ] Set up Travis CI and Netlify (@Chalarangelo)

Notes

• [1]: If you want, you can keep parts of the existing infrastructure (e.g. a testing system or something similar), as long as you maintain them and keep them up to date and provide us with guidelines and/or help during the migration process on how to integrate them to the new template.

Nothing is set in stone yet, but we are trying to get all repositories set up with the new template (check the 30-seconds-of-code and 30-seconds-of-python repositories to see what this looks like) and build it all up as soon as possible. However, we are asking each team to make sure there are as few issues with this as possible, so I'd love to get some feedback from you, guys. If you don't have time to participate in this procedure (which is absolutely fine), I and @fejes713 will take care of pretty much everything, so no worries, just respond below so that we know.

As title, some messages I think we need to be changed since this repository is the part of 30-seconds organization.

The messages are as follows:

Note: This project is inspired by 30 Seconds of Code, but there is no affiliation with that project.

This message I think should be removed/changed.

@sohelamin, what do you think about changing this description?

Despite "realiness" of following example I think it'd be good if it would be mistake proof, especially when it's something for others to learn from.

php > echo average(1,3,4,5);

3.25

php > echo average();

 

Warning: Division by zero in php shell code on line 3

NAN

php >

Migration procedure to the new common template for 30 seconds repositories.

This is still a work in progress, do not merge unless I explicitly say so!

Tasks

• [x] Update snippet structure to the new format
• [x] Rename to 30-seconds-of-php
• [x] Evaluate every snippet, check code, description, explanation, update as necessary
• [x] Update logo to match the style of the rest of the projects
• [x] Clean up the existing repository, remove anything not necessary
• [x] Copy files from the starter, configure accordingly
• [x] Update static parts, guidelines, issue/PR templates
• [x] Update Travis, add Netlify integration
• [x] Configure Google Analytics
• [x] Evaluate that all scripts (extractor, builder, webber) work as planned
• [x] Setup Netlify properly and merge, disable GitHub Pages (expect ~2 hours website downtime)