Add maps to your applications OutSystems Reactive Web apps with a single or multiple locations. Fully customizable and adaptable, allows you to change map behaviors, customize your map, add markers and customize each of them, according to your use case.
Maps made easy, from developers to developers. Use the OutSystems Maps to create visual rich enterprise-grade interfaces that help the user to quickly have map-based insights of the data.
- Built for Web and Mobile apps
- Simple to use and extend
- Add Markers, and Directions
- No javascript knowledge required
The OutSystems component, like all components, can be found in OutSystems forge. There you can also find a sample application that show-cases several uses of the component. The documentation for the component can be found in the official page, as well as, in a more interactive way in the Component living documentation.
If you're using OutSystems, this is how you can use this component in your application:
This repository contains the code that enable the usage of an external provider Google Maps to which you're required to obtain a license. The code is written in TypeScript🖤, and you are welcome to branch it and PR your changes/proposals!
We highly recommend the usage of the following tools:
- Visual Studio Code
- With these extensions:
- Document This
- ESLint
- Prettier - Code formatter
- Create a branch based in the branch master (lastest & greatest release)
- Open your Visual Studio Code in your branch
- Run the following command in Visual Studio Code terminal:
npm install(this will install all the dependencies that you need) - Do your magic! :)
- Document your code (with the extension "Document This", start typing
/**and the extension will give you a good starting point - Compile and fix errors and warnings (in Visual Studio Code terminal:
npm run build) - Check if the code format is following our conventions (in Visual Studio Code terminal:
npm run lint)- Some of the conventions can be fixed automatically by lint (in Visual Studio Code terminal:
npm run lintfix) - Although the script above execute the prettier conventions, you may want to run it over all project files (in Visual Studio Code terminal:
npm run prettier)
- Some of the conventions can be fixed automatically by lint (in Visual Studio Code terminal:
- Fix all errors & warnings! :)
- Create a PR, describing what was the (mis)behavior, what you changed and please provide a sample
- A new branch from master should be created.
- If possible the branch should be kept updated with the master branch.
- If possible unnecessary commit messages should be omitted.
After completing your changes, and testing, please proceed with submitting a Pull Request.
To be accepted, a Pull Request needs to:
-
Fulfill the following requirements
- Needs to compile without errors
- Needs to follow the code style rules (without warnings and errors)
- Needs to be approved by 2 team members (owners of the repo)
- The Pull Request template, should be filled up by the Pull Requestor:
- Provide a short description
- A link to a sample page showing the fixed behavior or the new feature
- What was happening?
- What was done?
- Tests steps
- Screenshots
- Checklist
-
Follow best practices
- The submitted code should be well documented (e.g. comments).
- Avoid changes outside the scope of the issue in hands.
- Avoid exposing sensible information of any kind (e.g. internal server link, process, etc).
- Download latest version in OutSystems forge
- Test the latest changes in the sample app
- Component living documentation
- Component documentation
Write us in the component support page!
Available internally on Slack channel #rd-uicomponents-contributors.
GitHub - OutSystems - Maps