Thank you for investing your time in contributing to our project! Any contribution you make will be reflected on the next release of MeteoalarmCard.
If you spot a problem in the project or want to propose a improvement or new integration to the project. Search if an issue already exists. If a related issue doesn't exist, you can open a new issue.
If you don't have MeteoalarmCard running locally please follow this setup guide.
- Install newest LTS release of Node.js, it has NPM package manager bundled with it.
- Fork this repository using Fork button. This will create a new
repository on your account named
<your username>/MeteoalarmCard
- Clone this repo to wherever you want:
git clone https://github.com/<your username>/MeteoalarmCard.git
- Go into the repo folder:
cd MeteoalarmCard
- Install dependencies (Node.js and npm are required):
npm install
- Run development server. It's going to watch source files, recompile on changes and server compiled file on local server.
npm start
- Add
http://localhost:5000/meteoalarm-card.js
to your Lovelace Resources. - Add
custom: Meteoalarm Card
to your Dashboard.
After successfully following this guide you should have card in your dashboard that is complied from your local code. Development server is going to recompile any changes that you make and after that you can see them after refreshing your Home Assistant tab.
- Fork the project and clone it to your local machine. Follow the setup guide.
- Before making any changes pull from the remote repository to update your main branch
git pull upstream master
- Create a branch on which you will be working.
git checkout -b update-polish-translation
- Commit your changes and push it to your fork of the repository.
- Make sure your changes are working locally. Run
npm run build
to check code style. - Create a Pull Request (PR). Make sure to describe the changes that you made and use the
Fixes: #number
keyword if you were working on a issue.
We are currently looking to implement more languages to MeteoalarmCard. If you are able to add or improve translations in language you speak don't hastate to make a PR.
Notes about current translation keys
editor.disable_swiper
- If there is not a good translation for swiper you can keep this word untranslated.editor.description
- These keys are used to generate helpful description for users selecting entities. Please make sure they sound correctly in all combinations. The formula isstart + any middle key + end
editor.description.warning_watch_statement_advisory
- If there is not a good translation for words (warning, watch, statement, advisory) you can keep these words untranslated.
If you want to improve existing translation:
- Follow the setup guide and contributing guide
- Modify the language file in the
src/localize/languages
directory - Remember that key that are not yet translated have
null
instead of the string. Please replace them with translated messages. - Open a Pull Request.
If you want to create a new translation:
- Follow the setup guide and contributing guide
- Copy
src/localize/languages/en.json
file and name it with appropriate language code. - Translate only the keys (second quotation mark).
- Import your translation in
src/localize/localize.ts
file. - Mention your translation in
README.md
file (list should be sorted alphabetically). - Open a Pull Request.